Zapier Webhook for your marketing workflow

How to receive a webhook in Zapier

AICMOHQ’s Zapier Webhook integration is planned, not connectable. The steps below explain Zapier’s receiving side for an existing event sender. They do not enable Studio event delivery from AICMOHQ, and no live AICMOHQ event schema or delivery guarantee is available yet.

1. In Zapier, create a Zap and choose Webhooks by Zapier as the trigger. Select Catch Hook for a parsed request body, or Catch Raw Hook when you need raw body and headers.
2. Copy the generated catch URL into the sending application’s private webhook configuration. Do not put it in browser code, a public repository or a screenshot.
3. Send a non-empty sample JSON event, then test the trigger and inspect the fields Zapier received. Map those fields into an action such as a CRM update or Slack message.
4. Test with non-production data, check the destination result, and turn on the Zap. Keep a stable event ID in your own sender so downstream actions can reject duplicates.

Example payload for a sender you control (illustrative only, not an AICMOHQ event contract): {"event_id":"demo-001","event":"draft.ready","title":"Review this draft"}.

Catch Hook vs sending a webhook

Catch Hook receives requests at a Zapier URL. A Webhooks action sends an HTTP request from Zapier to another service. An inbound hook is not a polling trigger, and receiving an event does not by itself publish a post. Choose the direction before configuring credentials.

Plans, limits and troubleshooting

Zapier’s webhook trigger guide lists Professional, Team and Enterprise support, not Free. It documents a 10 MB trigger payload limit and a 2 MB Catch Raw Hook limit; rate limits also apply. Confirm your current plan before building a workflow.

• No test event: confirm the sending URL, send a non-empty body, and inspect the sender’s HTTP response and Zapier trigger test.
• 404: Zapier documents this response when a Catch Hook Zap is turned off or deleted.
• Security: Zapier says to treat the catch URL as a secret. Do not assume it verifies your provider’s webhook signature. If authenticity checks are needed, validate them on a server you control before forwarding.

Provider documentation checked October 23, 2026. AICMOHQ setup will be documented when its backend is available; see current availability.