Skip to main content
Every flow that starts from Webhook received has a webhook address. Another system calls it with POST or GET, and the flow starts a run.

The address

The address is shown on the Trigger tab of the start step:
The flow id in the address is the only credential. Anyone who knows the address can start the flow. Treat it like a password and keep it out of public places.
The flow must be published and switched on. An address of a flow that does not exist, or that does not start from a webhook, answers 404. A flow that is switched off answers 410.

What the flow receives

The run receives the call as trigger data: The body may be up to 5 MB. A larger body is refused with 413. A call that starts a run answers 200 with { "data": { "runId": "..." } } at once, before the run has finished. Calls to one address are limited per caller and flow. Above the limit the answer is 429 with a Retry-After header.

Wait for the answer

Add /sync to the address when the caller needs the result:
The call starts a run and waits for up to 30 seconds:

Respond to webhook

Add Respond to webhook from the flow control plug at the point where the answer is known: The step sets the answer. The flow can go on with more steps afterwards. The caller does not wait for them.

Test a webhook

Switch the flow on and call the address, for example with curl:
Open the Runs tab to see the run and the data it received.
Last modified on October 26, 2026