ZAPIER WEBHOOKS
Zapier Catch Hook missing events — payloads that never arrived
Catch Hook triggers only fire on payloads received while the Zap is on and healthy. Payloads sent during downtime, off periods, or to stale hook URLs are discarded — and the sender’s logs still show a successful 200.
Why Zapier webhooks fail silently
The Zap was off when the payload arrived
Catch Hook doesn’t queue. Anything sent while the Zap is off is acknowledged then discarded.
Stale or copied hook URLs
Cloned Zaps, regenerated URLs, and copy-pasted test hooks leave senders POSTing to a URL that no longer maps to a live Zap.
Payload shape silently breaking the filter
If a Filter step rejects the payload, the run looks "successful" upstream — the data just never reaches the action steps.
The fix
- 1
Send a test payload and check Task History
If no task appears, the hook URL or Zap state is the problem. If a task appears but stopped at a filter, the payload shape changed.
- 2
Verify the sender is hitting the right URL
Compare the URL in the sender’s config against the Zap’s current Catch Hook URL character-for-character.
- 3
Audit filters, not just triggers
A silently-rejecting filter looks identical to a dead trigger from the sender’s side.
- 4
Keep a receipt of every delivery
HookShield logs each inbound payload before forwarding to Zapier — you can diff "sent" against "processed" and see exactly what Zapier dropped.
DEAD-MAN'S SWITCH
Never find out about a dead webhook from a customer again
Point Zapier at a HookShield ingest URL. Every delivery is logged, signed, and forwarded — and if pings stop arriving, you're alerted before the silence becomes an incident.