Skip to Content
Public Beta: Direct engineering support available. Join Discord →

How do you fan out a webhook to many destinations?

Fanning out a webhook means delivering one inbound event to N destinations, each with its own transform, its own filter, and its own retry pipeline. In Slashbin, one slow or downed destination never blocks the others — per-destination fault isolation is a contract of the platform, not something you build.

Slashbin is a webhook ETL and programmable gateway for developers and the AI agents that work alongside them. You own the Golden Model — one canonical schema per topic on each data stream — and every webhook is validated against it, then mapped into the shape each destination needs. Retry, replay, fan-out and the dead-letter queue keep that contract reliable, and the console, the CLI and an agent are three ways to operate the same system.

Fan-out protects the contract across destinations. The Multi-tool workflow below shows one webhook mapped for each tool, and the Golden Model page shows how that one contract is defined.

How it works in Slashbin

  1. Validate once at the edge. The inbound payload is checked against your Golden Model a single time — drift is rejected before any destination sees it.
  2. Each destination runs its own pipeline. Filter, transform to its Third-Party Model, deliver, retry — all independent per destination. When a destination's attempts run out, that delivery is permanently failed for that destination alone and shows in its delivery status.
  3. Failures are isolated. A destination that starts timing out gets its own circuit breaker and its own backoff. Deliveries to every other destination continue normally.
  4. Failed deliveries stay visible. When a destination recovers, you replay the event to send it again — the delivery that failed is visible in its delivery status, so you know which event to re-send.

When you need it

Multi-tool workflow

One order webhook feeds your CRM, your warehouse, and your analytics — each expects a different shape and has its own reliability profile.

Environment splits

Production and staging both need the same events, filtered differently, without one env's traffic contaminating the other's.

Adding a destination shouldn't be a deploy

Marketing wants Klaviyo, sales wants Slack alerts. Both are configuration in the gateway, not new code paths in your handler.

Fan-out at the gateway vs in your handler

ApproachWhat breaks
Fan out inside your webhook handlerOne slow destination holds the request open, others time out, the vendor retries the whole webhook, and now everyone sees duplicates.
Fan out via a message queue you ownYou now own consumers, retries, backoff, DLQs, and a runbook per destination — plus every schema change is a coordinated deploy.
Fan out at the Slashbin gatewayEvery destination is a configured pipeline with its own retries, its own circuit breaker, and its own filter. Adding a destination is configuration.

Feature detail

Per-Destination Fault Isolation

One destination failing never blocks or throttles another — every destination has its own retry queue and circuit breaker.

Per-Destination Filters

Route by rule — send subscription orders to your CRM only, test-tagged orders to staging, everything else to production.

Per-Destination Transforms

Each destination gets its own Third-Party Model derived from the Golden Model, so downstream shapes are decoupled from the source.

Independent Failure State

Attempts are bounded; when they run out, that delivery is permanently failed for that destination and shows in its delivery status, while deliveries to the other destinations are unaffected. To send the event again you replay it.

Deep dive

Learn how fan-out routing works in Slashbin.

View Setup Guides