Parallel Two-Channel Broadcast With Merged Webhook Response

How it works

1. 1.Webhook node accepts POST requests on path template/broadcast and defers the response to a response node
2. 2.A Set node reads body.message and defaults to 'Hello from n8n' when absent
3. 3.Prepare Message fans out simultaneously to Broadcast A and Broadcast B, each POSTing JSON with channel set to alpha or beta
4. 4.Merge node combines both HTTP results in combine mode by position
5. 5.Respond node returns the merged item as a JSON response to the caller

Use cases

• Starter template for practicing the fan-out/merge pattern before wiring real channels
• Broadcasting one notification to multiple channels such as Slack, Discord, or Telegram by replacing the HTTP nodes
• Verifying parallel execution and retry behavior of HTTP requests in n8n

Requirements

• The workflow must be activated (or the test URL used) for the Webhook to be reachable on your n8n instance
• HTTP nodes require no credentials since they call the public httpbin.org endpoint; retryOnFail is set with 2 retries
• Sending a message field in the JSON body is optional; otherwise the default value is used
• For production, replace httpbin.org URLs with real channel APIs and configure their credentials

Setup and testing in n8n

1. POST to the Webhook URL with Content-Type application/json and a body containing message
2. Send a request without message to confirm the default fallback value is used
3. Confirm two outbound POSTs reached httpbin.org with channel values alpha and beta
4. Inspect the JSON response returned to the client and verify it contains the merged channel results

Service Value

Ready-made workflow template for automation delivery and service execution.