How does the webhooks feature work?

To use the webhook feature while still in beta, you need to request access. If you’d like to do so, please email us at with a short description of how you’d like to use the feature so we can make sure your use case is well supported!

How the feature works:

You can pull incoming webhook data into a flow to use as data in the flow by using the Receive from webhook step that is now available in your builder. Initially, you’ll need to mock out the data that it is using, as it cannot pull data in while the flow is a draft. Once your flow is published, and catching webhooks, the mocked data will be replaced with the real data from each request. Read more here:

When you publish a flow, you’ll see a link to “Configure webhooks”. Click to enable webhooks on your flow and then copy the URL to give to your other service. There is also a graph of the requests and responses.

Every time a webhook is received, the flow will be queued up to run. It will not run more than once a minute, but other than that, it will run as much as it can. Runs happen in sequence, not in parallel, so multiple runs cannot happen at the same time. The complexity of your flow will dictate how long a run takes, and how long it takes to get to the next webhook.

If for some reason, your flow starts to run away, or you trigger way too many webhook requests, either tell me, or unpublish your flow to cut it off (shouldn’t be necessary, though).