What is webhook fan-out?
Webhook fan-out means taking a single inbound event and delivering copies of it to several destinations. It is also called broadcasting a webhook, a webhook splitter, or a webhook distributor. Most providers let you register only one URL per event — so if three systems need the data, you are stuck either building a relay yourself or begging each provider for extra endpoints.
NodeTrigger solves it in one step: point the provider at a single NodeTrigger route, then attach as many destinations as you need. Every matching event is duplicated and forwarded to all of them.
Send webhook to multiple destinations: Slack for the team, your CRM for the record, a data warehouse for analytics, and a backup endpoint for safety — from one inbound URL.
Common fan-out patterns
- Notify + record. Post an order to Slack and create a deal in your CRM at the same time.
- Duplicate a webhook to multiple endpoints. Send the same payment event to production and to a staging or backup service.
- Forward a webhook to multiple URLs across teams. One signup event feeds sales, marketing, and analytics independently.
- Route to multiple endpoints by condition. Combine fan-out with a payload filter so only high-value events reach every destination.
How fan-out works in NodeTrigger
On the visual canvas, a route branches from a source into one filter and then into one or more destinations:
POST /webhook ──▶ Filter: status = "paid"
├─▶ Slack #orders
├─▶ HubSpot deal webhook
└─▶ https://analytics.internal/ingestEach destination is delivered independently: if Slack is briefly down, the CRM and analytics still receive the event, and Slack is retried on its own with exponential backoff. Every destination can also carry its own payload transformation, so Slack gets a human-readable message while your CRM gets structured fields — from the same source event.
Reliable delivery to every destination
- Independent retries. Up to five attempts per destination with exponential backoff — one failing endpoint never blocks the others.
- Durable first. Every inbound webhook is written to a fail-safe JSON log before fan-out, so nothing is lost mid-delivery. See Fail-Safe Storage.
- Replay per event. Re-run any past event through your current destinations with one click. See Flow Log & Replay.
- SSRF-guarded. Only safe, public destinations are allowed; auth and cookie headers are never forwarded.
Frequently asked questions
How do I forward one webhook to multiple URLs?
Create a route, then add multiple destinations to it. Each incoming event is duplicated and delivered to every destination.
Is there a limit on the number of destinations?
No hard limit — attach as many destinations as your workflow needs to a single route.
What happens if one destination fails?
Only that destination is retried, independently, with exponential backoff. The others are unaffected.
Can each destination receive a different payload?
Yes. Apply a per-destination transformation so each endpoint gets the exact schema it expects.
One webhook in, many destinations out
Fan out incoming events to Slack, CRMs, analytics, and any URL — reliably, from a single endpoint.