Outbound Webhook Event Card

The Outbound Webhook Event card sends a custom flow.* event to your outbound webhooks mid-flow. Use it to tell other systems that a flow reached a checkpoint, such as an order confirmed or a lead captured. It needs a Pro plan or higher.

The card hands the event to the delivery queue and moves on at once. A slow or broken subscriber URL never blocks the flow.

Configuration

Setting	Description
Event name	Added after `flow.`. Type `order_confirmed` to send `flow.order_confirmed`. Empty sends the bare `flow` event.
Connection	Broadcast to all (default) sends to every connection subscribed to the event or to the `flow` namespace. Pick one outbound connection to send to it only.
JSON payload	Raw JSON for the event. It can use variables.

Event Name

The editor shows flow. before your input and the final name below it.

Input	Event sent
`order_confirmed`	`flow.order_confirmed`
`lead.qualified`	`flow.lead.qualified`
(empty)	`flow`

Use letters, digits, ., _ and -. Anything else is a validation error and the flow stops at this card.

JSON Payload

Variables are filled in before the JSON is parsed, so put quotes around text variables:

{
  "orderId": "{{webhook.order.id}}",
  "status": "confirmed",
  "customer": {
    "email": "{{flow.people.email}}"
  }
}

What subscribers receive in data depends on what the payload parses to:

Parsed JSON	Delivered `data`
Object	The object itself
Array or single value	`{ "value": <parsed> }`
Empty or malformed	`{}`. The flow continues.

Who Receives It

With Broadcast to all, every active outbound connection subscribed to the exact event, or to the flow namespace, gets the event. With a single Connection picked, only that one does. A connection subscribed to flow receives every flow.* event. Set subscriptions on the connection. For the envelope and headers, see Envelope & Delivery and Flow custom events.

Connections

1 input port. Receives execution.
1 output port. Always continues. The flow never waits for delivery.

Operations Cost

1 operation per execution. The card sends nothing to the contact.

Outbound Webhooks - connections, subscriptions and authentication
Webhook History - delivery attempts and retries