Forward webhooks to multiple destinations

One webhook in, every system updated. Add multiple output destinations to a bucket and Webhook Relay sends a copy of each incoming webhook to every output. Your provider only needs the bucket's single public URL.

Use this when you want to:

• Send payment events to your app, CRM, and accounting service.
• Deliver to production while also feeding a staging or analytics endpoint.
• Keep a copy in a logging or audit service without changing the sender.

Set it up in the dashboard

1. Open Buckets and select a bucket. If you need one, create a Public Destination first.
2. Under Routing → Output Destinations, click Add More.
3. Choose Webhook, enter a name and destination URL, select Public, then click Create.
4. Repeat for every URL that should receive the webhook.

Copy the bucket's input URL into your webhook provider once. New destinations can be added later without updating the provider.

Set it up with the CLI

Install and sign in to the CLI, then create one bucket and add public outputs to it:

relay bucket create payments

relay output create primary-api \
  --bucket payments \
  --type public \
  --destination https://api.example.com/webhooks

relay output create audit-copy \
  --bucket payments \
  --type public \
  --destination https://audit.example.com/events

Run relay bucket inspect payments to view the bucket and its public input endpoint. Give that one endpoint to the webhook sender; Webhook Relay handles the fan-out.