ZAPIER WEBHOOKS
Zapier REST hook stopped firing — unsubscribed without notice
REST hook triggers rely on a subscription kept alive by your API. When unsubscribe/handshake calls fail — or the subscription quietly expires — the trigger simply stops firing. No error, no Zap state change, just no events.
Why Zapier webhooks fail silently
Failed subscribe/unsubscribe handshakes
Zapier verifies subscription endpoints during setup and teardown. If your API errors on these calls, the subscription never registers — or dies silently later.
Subscription expiry
Some APIs expire REST hook subscriptions. When it lapses, events fire at nothing and the Zap looks healthy in the editor.
Auth drift
Rotated API keys or changed OAuth scopes break the hook delivery path without breaking the Zap’s visible configuration.
The fix
- 1
Test the trigger in the editor
Use "Test trigger" — if it can’t pull a sample, the subscription is dead and needs re-creation.
- 2
Recreate the subscription
Turn the Zap off/on or re-test the trigger to force a fresh subscribe call to your API.
- 3
Check your API’s hook logs
Verify the subscribe call actually landed and that deliveries are being attempted to Zapier’s target URL.
- 4
Log deliveries externally
If your platform emits webhooks, route them through HookShield first — a silent unsubscribe becomes a visible drop in the event stream.
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.