This article provides a complete, practical walkthrough of the Splitout Webhook Import Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automating Scaleway Server Discovery and Filtering with n8n: A Scalable Workflow Guide
   
   Meta Description:  
   Learn how to build a powerful n8n workflow that fetches and filters Scaleway server data across multiple zones using customizable criteria like name, public IP, tags, or zone.
   
   Keywords:  
   n8n, Scaleway API, server automation, public cloud, workflow automation, Scaleway instance, baremetal server, DevOps, webhook, API automation, server inventory, infrastructure management
   
   Third-Party APIs Used:
   
   - Scaleway Instances API (https://api.scaleway.com/instance/v1)
   - Scaleway Baremetal API (https://api.scaleway.com/baremetal/v1)
   
   Article:
   
   Automating Server Discovery Across Scaleway Zones Using n8n
   
   For modern DevOps teams, managing large-scale cloud infrastructure requires both visibility and automation. Scaleway, a flexible IaaS provider, offers both virtual and baremetal servers across multiple geographic zones. In this guide, we’ll walk you through an advanced n8n workflow designed to automate the discovery, aggregation, and filtering of Scaleway server information—with built-in search capabilities via an authenticated webhook.
   
   This low-code solution is robust, highly configurable, and serves as a reusable building block for cloud infrastructure automation.
   
   Why Automate Scaleway Server Management?
   
   Manual queries across API endpoints or within cloud dashboards can quickly become error-prone and time-consuming. Automating this task with a workflow built in n8n provides multiple advantages:
   
   - Unified view of instance and baremetal servers across zones
   - Real-time search via HTTP requests or API endpoints
   - Filtered insights based on name, tags, public IP, or zone
   - Seamless integration with internal systems or tools
   
   How It Works: End-to-End Breakdown
   
   1. Trigger via Webhook with User Input
   
   The workflow starts with a Webhook node that listens for POST requests. It expects two parameters:
   - search_by: The type of filter you want to use (e.g., tags, public_ip, name, or zone).
   - search: The keyword to use when filtering the results.
   
   Basic Authentication is required, ensuring secure access to the endpoint.
   
   2. Define Configuration and Search Criteria
   
   The Edit Fields node sets up key variables including:
   - Zones to target for instances and baremetal servers
   - Scaleway X-Auth-Token for API access
   - Incoming search parameters
   
   These dynamic parameters allow the workflow to adapt to different queries and API authentication methods.
   
   3. Dynamically Retrieve Server Data
   
   The workflow supports both Scaleway’s Instances and Baremetal APIs and works across multiple zones. Using a loop construct (Split and Loop Over ZONE_INSTANCE), it sends concurrent API requests to fetch all available servers in the specified zones.
   
   Key endpoints include:
   - GET https://api.scaleway.com/instance/v1/zones/{zone}/servers
   - GET https://api.scaleway.com/baremetal/v1/zones/{zone}/servers
   
   The workflow distinguishes between instance and baremetal zones using a conditional (IF) node.
   
   4. Aggregation and Data Shaping
   
   The fetched responses are normalized and combined using a Code node. This node performs:
   - Parsing of input data
   - Extraction of metadata (name, tags, public IP, user, server type, zone, etc.)
   - IP handling logic to choose between IPv4 and IPv6
   - Uniform formatting for easy consumption
   
   Helper functions within this node include:
   - extractServers()
   - getPublicIPs()
   - getUser()
   
   5. Dynamic Filtering
   
   Once all servers are collected into a single dataset, a Switch node routes the data to different Code nodes depending on the requested filter type:
   - Code search Tags
   - Code search Name
   - Code search Public IP
   - Code search Zone
   
   Each filter node compares server attributes with the search keyword and returns filtered results. If the “search_by” value is invalid or null, the workflow responds with a JSON error identifying valid filter options.
   
   6. Respond to Request
   
   The filtered results (or error message) are returned to the requester through corresponding Respond to Webhook nodes.
   
   Each search type has its own webhook response node to isolate execution paths and keep the response modular.
   
   Example Usage Scenario
   
   Let’s say a DevOps engineer wants to find all servers tagged with Apiv1. A simple POST request to the webhook URL could look like this:
   
   POST /a6767312-3a4c-4819-b4fe-a03c9e0ade5c (with basic auth)
   
   Body:
   {
     "search_by": "tags",
     "search": "Apiv1"
   }
   
   In response, the workflow will return all servers that match the tag "Apiv1," including metadata such as name, IP address, zone, type, and assigned user.
   
   Security Note:
   Before deploying the workflow, don't forget to replace the placeholder “Scaleway-X-Auth-Token” with your actual token from the Scaleway console.
   
   Use Cases
   
   - Inventory management of multi-zone cloud infrastructure
   - On-demand querying of server metadata for monitoring/alerting
   - Infrastructure as code (IaC) integration
   - Automation layer for internal tools and applications
   
   Conclusion
   
   This n8n workflow is a versatile tool for DevOps practitioners, SREs, and developers who manage infrastructure on Scaleway. By combining flexible HTTP triggers, dynamic API requests, and intelligent filtering—all in a low-code environment—you get a workflow that not only saves time but also reduces the risk of errors in managing cloud resources.
   
   Integrate it into your internal tools or CI/CD pipelines, and you’ve got a scalable, real-time server discovery solution at your fingertips.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.