Trigger from a Webhook
When you want another system, such as a website form or your CRM, to start a workflow the moment something happens, you use a webhook. It gives your workflow a private URL that the other system calls, and the details it sends come into the run so later steps can use them.
Nodes involved
- The Start node, configured as a webhook trigger.
How to build it
Configure the Start node as a webhook
On the Start node, set it up as a webhook trigger and define the fields you expect the caller to send. See Triggers & Webhooks for the full detail.
Get the URL
Publish the workflow to get its webhook URL. Only published workflows have a working URL, and it is private, so only systems authorized to act for your organization can call it.
Reference the incoming data downstream
The information the caller sends is available to later steps through the Start node. Point a field at an incoming value like this:
Use whichever field names the caller actually sends.
Test it
Send a sample request to the URL and watch the run in Testing & Debugging to confirm the incoming data arrived where you expect. While you are still building, you can also start runs by hand from there.
A webhook URL is not a public, open endpoint. The caller must be authorized to act for your organization, so only trusted systems you have set up can start your workflows.