Automation
Webhook Trigger
Starts the flow when another system calls its own web address — an order system POSTing each new order, say — with the call's body as the first rows.
When to use it
Use it when a flow should run the moment something happens elsewhere, rather than on a schedule.
In a pipeline
Webhook TriggerJSON Parse / FlattenSQL Server Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Path | text | Yes | orders/new |
| Method | select | — | post |
| Shared secret | password | Yes | At least 16 characters |
| Answer the caller | select | — | accepted |
| Calls allowed per minute | number | — | 60 |
Example
Start on a new order
- Path=orders/new
- Method=POST
| order_id | total |
|---|---|
| A-1 | 120 |
A JSON list becomes one row per item; an object one row; CSV one row per line; form fields one row.
Worth knowing
- The address is shown in the node's settings once the flow is saved: /api/hooks/<flow id>/<path>.
- Callers prove they know the shared secret by signing the body: X-FlowDoo-Signature: sha256=<HMAC-SHA256 of the body>. Senders that cannot sign may send X-FlowDoo-Secret instead. Anything else gets 404.
- Calls allowed per minute protects the flow from a sender in a loop (429 with Retry-After).
- Answer the caller at once (202) unless the caller needs the result: senders retry when an answer is slow.