# Zapier Webhook

<!-- meta: type=event-zapier; location=Custom Events; category=Trigger; platforms=Joomla and WordPress (where applicable) -->

## Overview

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.

## Why use this node

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:

- Start automation when zapier webhook receives data or fires on schedule
- Pass structured payload fields to downstream steps without custom PHP
- Keep business logic visible on the canvas instead of hidden in plugins

## When it runs

Zapier (or any HTTP caller) POSTs to your flow's Zapier webhook URL when an automation step runs.

## Example workflows

Common patterns on the canvas:

1. **Trigger or Webhook** → upstream steps → **Zapier Webhook** → **Send Email** or CMS update
2. **Scheduled trigger** → **Zapier Webhook** → **Debug** (while testing) → production action

## How to set it up

Map incoming payload fields on the Design tab for use in later nodes.

## Properties panel

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 |

### System (automatic — not edited by the user)

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 | — | — |

### User-configured — General tab

| 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 | — | — |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `description` | Description (optional) | `textarea` | No | — | Description of the Zapier webhook |

### CMS site configuration (not on this node's properties panel)

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.

## Output payload 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. |

## Related nodes

Other steps in the same area of the palette:

- **Jorchestrator Cron** (`event-jorchestrator`) — Custom Events
- **PayPal Payments Pro** (`event-paypal`) — Custom Events
- **Stripe** (`event-stripe`) — Custom Events
- **Webhook** (`webhook`) — Custom Events