When it runs: Zapier (or any HTTP caller) POSTs to your flow's Zapier webhook URL when an automation step runs.
When it runs: Zapier (or any HTTP caller) POSTs to your flow's Zapier webhook URL when an automation step runs.
External no-code automations can start JOrchestrator flows with a JSON body.
When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the Design tab.
Zapier Webhook is a trigger in the Custom Events group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.
Typical reasons teams add Zapier Webhook to a flow:
Zapier (or any HTTP caller) POSTs to your flow's Zapier webhook URL when an automation step runs.
Common patterns on the canvas:
Map incoming payload fields on the Design tab for use in later nodes.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| AI | Optional assistant for trigger setup (paid plans) |
| Design | Trigger configuration, payload schema, and inbound settings |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
inputSchema | Webhook Payload Schema (optional) | json-schema (default: [object Object]) | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
webhookUrl | Webhook URL (optional) | text | No | — | https://hooks.zapier.com/hooks/catch/... |
apiKey | API Key (optional) | secret-text | No | — | Zapier API key |
verifySignature | Verify Signature (optional) | toggle (default: false) | No | — | — |
requireHttps | Require HTTPS Only (optional) | toggle (default: true) | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
description | Description (optional) | textarea | No | — | Description of the Zapier webhook |
Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.
After this step runs, later nodes can reference these fields using placeholders such as {{zapier_webhook.event}}.
| Field key | Type | Description |
|---|---|---|
event | object | Inbound webhook event envelope. |
data | object | Inbound event data payload. |
Other steps in the same area of the palette:
event-jorchestrator) — Custom Eventsevent-paypal) — Custom Eventsevent-stripe) — Custom Eventswebhook) — Custom Events