The Webhook trigger gives your workflow a unique inbound URL. Anything that posts data to that URL, an external app, a third-party form, or a script, starts the workflow and passes its payload downstream.
When to use it
Use it to connect apps and services that are not covered by the built-in form triggers, or to receive data from a custom HTML form on any site.
Configuration
- Add a Trigger node and choose Webhook from the External group.
- The node generates a unique Webhook URL. Use the copy button to grab it, and the info button for setup examples.
- Point your external app or form at that URL as its submission endpoint.
- Send a test payload, then use Get Samples to capture the incoming keys automatically. Each key becomes a value you can reference downstream.
Defining keys
You have two ways to tell the node which fields to expect:
- Get Samples: send a real request, and the node reads the keys from the sample payload.
- Add Manual Key: type a key name and pick its type (string, number, or boolean) to define it by hand.
Example HTML form
<form action="YOUR-WEBHOOK-URL" method="post"> <input type="text" name="user_name" placeholder="Name"> <input type="email" name="user_email" placeholder="Email"> <button type="submit">Submit</button> </form>
Using payload fields
[[user_email] from trigger-1] [[user_name] from trigger-1]
Use [Input from trigger-1] for the whole payload. See Data Flow and Variable Handling.
Local and Cloud
The trigger costs no credits. Inbound webhooks are most reliable in Cloud mode, where the hosted engine receives the call and runs the workflow without PHP timeouts. See Local vs Cloud execution.
Related
- Trigger Nodes
- Output Node (return results to the caller)
- Data Flow and Variable Handling
Was this helpful?
Contact us