Webhook Triggers and Zap Actions - Service Disruption

What to do

• Check whether your product depends on Zapier. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 2m it lasted.

  Anything that failed between 2026-09-08 14:06 UTC and 2026-09-08 17:08 UTC may need a replay.

• Subscribe to Zapier's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=zapier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Zapier 2

1. monitoringSep 8, 2026, 2:06 PM UTC

   A brief infrastructure issue between approximately 8:15–9:50 AM ET caused some Zap workflows using webhook triggers to not fire, and some Zap action steps to fail. The issue has been resolved, and Zap Runs are processing normally. We're reviewing affected accounts and replaying missed webhook events where possible. If you notice a Zap that should have run during this window and did not, contact Support: [zapier.com/app/get-help](http://zapier.com/app/get-help "zapier.com/app/get-help")

   provider

2. resolvedSep 8, 2026, 5:08 PM UTC

   The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved. If you're still seeing issues with a Zap that should have run during this window, contact Support: [zapier.com/app/get-help](http://zapier.com/app/get-help "zapier.com/app/get-help")

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.