Zapier webhook not triggering?

You set up a Webhooks by Zapier → Catch Hook trigger, pointed your app at the hooks.zapier.com/hooks/catch/… URL, and the Zap never runs — or the test step sits on "waiting for a request". This failure has a short, ordered list of causes. Work through them top to bottom; the first two catch most cases.

0. First: split the problem in half

Is the sender not sending, or is Zapier not accepting? Prove each side separately.

Prove Zapier's side by sending a request you control. The simplest test needs only a browser — paste your webhook URL into the address bar with a query parameter appended:

https://hooks.zapier.com/hooks/catch/123456/abcde?field_name=test_value

A working hook answers with a small JSON body containing "status": "success" (plus attempt/request IDs). Or send a proper POST from a terminal:

$ curl -X POST -H 'Content-Type: application/json' \
    -d '{"first_name":"Ada","plan":"pro"}' \
    https://hooks.zapier.com/hooks/catch/123456/abcde

If that works (check Zap history / Test trigger), Zapier is fine — the problem is what your app sends, or that it sends nothing at all.

Prove your app's side by pointing it at a capture URL instead of Zapier for one delivery:

$ curl https://hookden.pages.dev/new

Swap the /h/… URL into your app's webhook setting and fire the event. Now you can see the exact method, headers, and raw bytes your app sends — including whether the body is really JSON or secretly form-encoded, XML, or something Zapier can't parse (cause 4 below). Zapier's own troubleshooting docs recommend exactly this inspect-outside-Zapier step. Once the capture looks right, replay it straight to your hooks.zapier.com URL from the bin (one click, byte-identical body) to prove Zapier accepts the real payload — no need to trigger the event again.

1. Webhooks by Zapier needs a paid plan

The Catch Hook / Catch Raw Hook triggers are a premium feature — they're available on Professional, Team and Enterprise plans, not on the Free plan. On a free account the step simply won't work, and this is easy to miss because the editor still lets you explore it. If you're on Free, this is your answer; everything below assumes the plan requirement is met.

2. The Zap is off — or was off recently

When a Zap using Catch Hook is turned off or deleted, its URL eventually returns 404 — but there's a system update delay of up to several hours during which the URL still answers 200 while doing nothing. Two nasty consequences:

• Your sender gets 200s, retries nothing, and the deliveries silently vanish.
• After turning a Zap back on, don't trust a lone success response from minutes earlier as proof it was captured — check Zap history for actual runs.

3. Wrong trigger for the request type

• Your app makes POST/PUT requests with a body → use Catch Hook (parsed fields) or Catch Raw Hook (unparsed body up to 2 MB, headers included).
• You want Zapier to poll a URL with GET and check for new entries → that's the separate Retrieve Poll trigger, not Catch Hook.

4. Unsupported payload format

Catch Hook parses JSON, XML, or form-encoded bodies only. Payloads that commonly break it: multipart/form-data uploads, plain text, bodies whose Content-Type says JSON but whose bytes aren't valid JSON. Symptoms range from missing fields to the trigger never producing a usable record.

• Capture one real delivery (step 0) and look at the raw body next to its Content-Type header — mismatches jump out immediately.
• If the structure is unusual, switch to Catch Raw Hook and parse it yourself in a Code step, or use Pick Off A Child Key on Catch Hook to grab a subset.

5. Test-trigger timing

When testing in the editor, send the request first, then click Test trigger promptly. If you wait too long the editor may not find the recent request — fire the event again and retest immediately.

6. Authentication limits

Webhooks by Zapier supports Basic auth only. If your sender insists on OAuth, token exchanges, or signature handshakes, the generic webhook trigger can't do it — that's Zapier Developer Platform territory. (If the sender requires the receiver to answer a verification challenge, a capture bin with a templated response can often pass it — see the Slack and Zoom guides.)

7. Throttling and delayed runs

Under load, two different things can happen:

• 429 Too Many Requests — the documented limits are 20,000 requests per 5 minutes per user, and 1,000 per 5 minutes per Zap on legacy webhook routes. Senders should retry non-200 responses with exponential backoff.
• 200 but delayed — during high webhook activity Zapier may accept the request and delay processing by several minutes. The Zap isn't broken; check Zap history a little later before concluding the webhook was lost.

8. The sender needs a specific response

Zapier always answers a fixed JSON 200 for Catch Hook, and it can't be customized. If your sender requires an empty response body, use Catch Raw Hook and add silent/ to the end of the webhook URL. If the sender requires anything fancier (an echoed token, a computed hash), Zapier's trigger can't produce it — test what the sender actually requires against a capture bin first, where the response status, headers and body are fully configurable.

Recap: the five-minute isolation flow

1. Browser-GET the hook URL with a query param → expect "status":"success".
2. Point the sender at a capture bin → confirm it sends at all, and inspect the raw bytes + Content-Type.
3. Replay the captured request to the hooks.zapier.com URL → check Zap history.
4. Whichever of those three steps fails is where the bug lives.

Related

Same debugging job on Make: Make.com webhook not triggering — where the trap is a 200 "Accepted" that quietly parks your request in a queue.

← All guides · Signature debugger · Payload examples · Docs · Hookden vs webhook.site