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:
The workflow
The upstream’s JSON body arrives directly asinput. 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:
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.userisnullon 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.idfor Stripe,input.event_idfor Slack). GitHub’s is header-only atinput.__webhook.headers['x-github-delivery']. Inbound headers are lowercased (authorization/cookiestripped). - One webhook per workflow. For two upstreams, create two workflows sharing helper code.
inputSchemaisn’t enforced on webhook fires, and its defaults aren’t filled in. Read optional fields asinput.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.