Run parallel webhook services with HTTP Request fan-out

Quick overview This workflow fans out three concurrent HTTP POST requests to internal n8n webhook endpoints, simulates independent service runtimes, and returns a report showing timing, ordering, and whether the tasks overlapped to confirm they ran in parallel.

How it works Starts manually and prepares three items that each contain a target webhook URL and a payload. Combines the three items into a single list and sends them as concurrent HTTP POST requests using n8n’s HTTP Request node with batching disabled. Each webhook endpoint (service-1, service-2, service-3) starts its own execution, records a start timestamp, and simulates work by waiting for a different duration. Each service responds to the original HTTP request with JSON containing the service name, startedAt, endAt, and the executionId. Aggregates all service responses and calculates overlap and timing metrics (wall time vs summed durations), plus arrival and finish order, to verify parallelism.

Setup Replace https://YOUR-N8N-URL in the three service definitions with your n8n instance base URL so the HTTP requests reach your webhook endpoints. Activate the workflow so the production /webhook/service-1, /webhook/service-2, and /webhook/service-3 endpoints are available. (Optional) Adjust the wait durations and the HTTP Request timeout to match your real tasks when you swap the simulated waits for actual work.

Additional info Need help? If you're facing any issues using this workflow, join the community discussion on the n8n forum.