Auto-forward & targets
Replay targets
A replay target is a URL where captured webhooks are forwarded. Each team member creates their own target pointing at their local dev server. Targets are scoped to an endpoint — they only receive captures from that endpoint.
To add a target, expand an endpoint in your project and click Add Target. Enter a name (e.g., "My laptop") and the URL (e.g.,
http://localhost:3000/webhooks).
Auto-forward
Enable the Auto-replay toggle on a replay target to automatically forward every incoming webhook to that target as it’s captured. No manual replay needed — webhooks arrive at your dev server in real time.
| Plan | Auto-forward targets |
|---|---|
| Deckhand | 0 |
| First Mate | 1 |
| Captain | 3 |
Forward to multiple targets (fan-out)
A single capture can auto-forward to more than one target at once. Mark several targets on an endpoint as auto-forward and every incoming webhook lands on all of them in parallel. Send the same Stripe event to your payment handler and your analytics service without firing the webhook twice. The number of auto-forward targets per capture scales with your plan, as shown above.
Need different shapes per destination? Pair fan-out with Transformations: routing can send each transformed version of a capture to its own target automatically. See Transformations.
For one-off bulk sends, batch replay selects multiple captures and sends them across multiple targets in one action (N captures by M targets). Batch replay is available on First Mate and up.
CLI forwarding
The FlurryPORT CLI can forward captures to your local machine without setting up a replay target in the UI. See CLI setup for details.