Skip to main content

​
What is this?

Receive Webhook starts a workflow whenever an external system sends a request to the workflow’s webhook URL — an order placed in your store, a form submitted on your site, a status update from another tool. It’s how automations react to events that happen outside the conversation.

​
How to use it

1

Create the workflow

Go to Automation → Create Automation, choose the channel, and pick Receive Webhook as the Trigger Type. See Create a Workflow.
2

Copy the webhook URL

The trigger gives you a unique URL for this workflow. Add it to the external system that should call it.
3

Protect it (optional)

Add a signing secret so the webhook only accepts requests signed with it. See Protect a webhook with a signing secret.
4

Use the payload in later steps

Whatever the request sends becomes available as variables — for example {{webhook.order.amount}} — for use in messages, conditions, and updates. See Variables.
5

Test, then activate

Send a sample request (or trigger the real event once) and check the result in Inbox and Analytics, then activate — see Manage Live Flows.

​
Tips

  • Send only what you need. A smaller, well-shaped payload is easier to map into variables and debug.
  • Route by payload with Condition Branch. One webhook trigger can serve several outcomes — for example different order statuses — by branching on a field in the payload.

​
Troubleshooting / Technical Notes

  • The flow never runs. Check that it’s Active and that the external system is calling the correct webhook URL for this workflow. Open Webhooks to see whether the request arrived at all, and why it failed.
  • A variable shows {{…}} instead of a value. The field name doesn’t match what the payload actually sent — check the request body and the variable name.
  • The flow runs on every request, even bad ones. Add a Condition Logic step early in the flow to validate the payload before acting on it.
Last modified on September 24, 2026