Scaleway Server Information Retrieval Workflow

This workflow is ideal for:

• Developers and DevOps Engineers: Who need to automate the retrieval of server information from Scaleway, saving time and reducing manual effort.
• System Administrators: Looking for a streamlined way to manage and monitor server instances and baremetal configurations across multiple zones.
• Technical Support Teams: Who require quick access to server details for troubleshooting and support purposes.
• Data Analysts: Interested in analyzing server data based on specific criteria like tags, names, public IPs, or zones to derive insights.

This workflow addresses the challenge of efficiently retrieving and filtering information about Scaleway servers. It allows users to:

• Automatically gather server data from multiple zones, reducing manual API calls.
• Filter the results based on various criteria such as tags, names, public IP addresses, or zones, enabling targeted data retrieval.
• Return structured server information quickly through a webhook, facilitating integration with other applications or workflows.

1. Webhook Activation: The workflow starts when a POST request is sent to the webhook, containing parameters like search_by and search to define the filtering criteria.
2. Edit Fields Node: This node captures and prepares the incoming search parameters along with necessary configuration details, including the Scaleway authentication token and zone definitions.
3. Splitting Zones: The Split Out ZONE_INSTANCE node divides the predefined zones for separate processing.
4. Loop Over Zones: The Loop Over Zone Instance node iterates through each zone, making appropriate API calls to retrieve either instance or baremetal server data based on the zone type.
5. Data Aggregation: A Code node consolidates the server data from all zones, extracting essential details like names, tags, public IPs, types, states, zones, and users.
6. Dynamic Filtering: The Switch node evaluates the search_by parameter and routes the data to specific filtering nodes based on the chosen criteria.
7. Responding to Webhook: Filtered results are sent back to the requester via designated Respond to Webhook nodes, with error handling for unsupported search criteria.