Webhook
Starts the automation when an external system sends an HTTP POST to a URL generated for this trigger. Reach for it when the system you want to react to can call out to you but has no integration of its own.
Fields
| Field | Description |
|---|---|
| Name | What the trigger is called on the canvas. Once the trigger has been saved, its Webhook URL and Signing secret are shown beneath this field—that pair is what you hand to the sending system. |
| Example Request | A read-only, copy-paste-runnable shell example for this trigger's endpoint. It shows the sender computing the signature from the secret and the exact request body, rather than a fixed value, because that is how the signature has to be produced on every request. |
The URL is derived from the trigger and rebuilt on every save, so it survives the server being moved. The signing secret is generated the first time the trigger is saved and kept stable afterwards, so the copy held by the sending system stays valid.
Node actions
Once the URL and signing secret exist, the node's menu offers two actions:
- Fire Test—send a test delivery to confirm the wiring end to end.
- Deliveries—review past delivery attempts, including ones that were rejected.
What later steps see
The trigger's output is whatever the caller posted—so its shape is not knowable before an event arrives, and the trigger declines to invent one. This has a practical consequence worth knowing: a reference into the webhook's payload cannot be checked against a schema, so the editor leaves such references unverified rather than flagging them as broken. Build the flow against the shape you expect, fire a test delivery, and read the real payload back from the run.