Skip to main content
Add a webhook trigger to a workflow. It’s an additional trigger, so the workflow stays request-callable too. Zite mints a stable ingress URL per webhook workflow:
Possession of the URL is the auth. The secret token is baked into the path (the Zapier / Make / Airtable model). Paste it into the upstream’s dashboard; no separate HMAC or signing secret.

The workflow

The upstream’s JSON body arrives directly as input. Nothing parses it against inputSchema on a webhook fire, so a schema can’t turn deliveries away. Gate on the event type at the top of execute instead, and return a success value for anything else so the provider stops retrying it:
After you add the workflow, the URL surfaces in the chat’s webhook panel and the app’s Webhooks settings tab. Fire one test event to capture a real payload and refine inputSchema.
Webhook workflows are set up in the Zite editor, not over the Zite MCP, because the editor mints the URL and captures the test payload. When building through the MCP, build everything else, then open the app in the editor (the editorUrl from commit) and ask its agent to add the webhook trigger.

Rules

  • context.user is null on webhook fires. The event body is your only input.
  • Respond within ~30s. Upstreams retry on timeout, re-running your code.
  • Dedup on a stable delivery id, usually in the body (input.id for Stripe, input.event_id for Slack). GitHub’s is header-only at input.__webhook.headers['x-github-delivery']. Inbound headers are lowercased (authorization / cookie stripped).
  • One webhook per workflow. For two upstreams, create two workflows sharing helper code.
  • inputSchema isn’t enforced on webhook fires, and its defaults aren’t filled in. Read optional fields as input.x ?? fallback. Let a genuinely malformed payload throw so the run shows up in run history.
  • Scope the upstream to send only the event types you handle, or your workflow runs on every event it fans out.
See the Webhooks reference for the URL format and per-workflow token env var.