Webhook Fanout — One URL, Multiple Destinations
Receive a single inbound webhook and have Requex forward it to as many HTTP endpoints as you need — each with its own retry count, timeout, and custom headers.
Short answer: In Requex Settings → Forwarding, add one rule per destination URL. Every inbound request triggers all rules in parallel. Requex returns a response to the sender immediately — it doesn't wait for your downstream services.
When You Need Fanout
Most webhook providers — GitHub, Stripe, Shopify, Twilio — only let you register one destination URL per event type. If you need the same event to reach your CRM, your Slack channel, your analytics pipeline, and a custom microservice, you normally need to build a fan-out router on your own server.
Requex handles this without a server. Each forwarding rule fires independently. A slow or failed destination doesn't affect the others.
How Forwarding Rules Work
| Setting | What it does | Typical value |
|---|---|---|
| URL | Where to forward the request | https://your-service.com/hook |
| Method | HTTP method to use | POST (or match inbound) |
| Pass-through body | Forward the original request body | Enabled |
| Pass-through headers | Forward original headers | Enabled |
| Retry attempts | Retries on non-2xx response | 3 |
| Timeout | Max wait per attempt | 10s |
| Enabled | Toggle rule on/off | true |
After each delivery attempt, Requex writes a forwarding log entry to the request record. You can inspect exactly which rules succeeded, which retried, and the response from each destination — in the request detail view.
Example: GitHub Push → 4 Destinations
Start fanning out in 60 seconds
Free, no signup. Add as many forwarding rules as you need.
Open Requex →Related use cases
Start Testing Webhooks Now
Generate your unique URL and test webhooks instantly. Free, no signup.
Open Webhook Tester →