Send webhooks from a flow
Available on Business Enterprise Who can do this: Client Admin Updated 30 Oct 2026
A Send webhook card posts an event name and a JSON body to your CRM, Zapier, Make, n8n or your own endpoint while the flow runs.
Add a destination
- Open Settings → Integrations → Webhooks.
- Select Add destination. Enter a Name and a URL, which must be a public address starting with
https://. - If your endpoint needs an Authorization header, add it under Extra headers. Select Save.
- Select Verify. Send4 sends a test request to the address, using the event name
send4.test.
Note The address and any headers are stored in the destination’s settings. They never show in the flow or in a run’s history.
Caution A card can only use a verified destination. If you change the URL or headers, select Verify to verify the destination again.
Add a Send webhook card to a flow
- Open the flow, select Add step and choose Send webhook.
- Connect it to the outcome where the data should go out, by dragging that outcome to the card.
- Choose the Destination, and fill in Event name, such as
lead.qualified. - Edit Body (JSON). It’s the exact JSON your endpoint receives. Put text variables inside quotes, such as
"{{ lead.name }}", and leave numbers bare. - Select Done. If the flow isn’t live yet, select Activate.
Caution On Starter you can add this card, but it doesn’t post anything. It takes its failed outcome every time.
Check that it arrived
- Open Settings → Integrations → Webhooks.
- On the destination, select the history icon to open Recent deliveries.
- Check each delivery’s Status: Delivered, Failed or Pending.
Caution The card’s sent outcome means the webhook is queued, not delivered. The flow carries on either way, so Recent deliveries is where you see a failure.
Caution A run in Test flow sends the webhook for real. Your endpoint can tell test runs apart by the
X-Webhook-Simulated header. Was this helpful? Tell us what’s missing Still stuck? Email [email protected]