Live / Zapier / Incident
Zapier: Webhook Triggers and Zap Actions - Service Disruption
Zapier · zapier.comMinor incidentResolved2026-09-08 14:06 UTC
Public — what happened
Summary
Zapier said that some automated workflows relying on webhook triggers did not start, and some action steps within workflows failed, during a window of roughly 8:15 to 9:50 AM ET on September 8, 2026. The company attributed the disruption to a short-lived infrastructure problem and rated it minor. Zapier said workflows are now running normally, though the incident remains under monitoring while it checks affected accounts and re-sends missed webhook events where it can. Users who believe a workflow should have run during that period but did not were asked to reach out to Zapier support.
Timeline
- Started — 2026-09-08 14:06 UTC
- Resolved — 2026-09-08 17:09 UTC · 3h 03m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Zapier against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Zapier: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zapier report →
More from Zapier
Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.