Zapier zap not triggering? The 7 usual causes

A Zap that stays silent feels like a broken product. It almost never is. Work down this list in order — the cause is usually in the first three.

1. The Zap is on, but the version you edited isn't published

Editing a live Zap creates a draft. If you didn't publish, the old version is still the one running. Open the Zap and confirm the change you made is in the published version, not just the editor.

2. Polling triggers wait

Only some triggers are instant. Polling triggers check on a schedule that depends on your plan — often every one to fifteen minutes. Nothing is broken; you're early. Use "Run Zap" to test rather than waiting.

3. Triggers only fire on new records

A "new row" or "new item" trigger ignores anything that existed before the Zap was switched on, and often ignores rows edited rather than added. Create a genuinely new record to test.

4. A filter or path is quietly stopping it

Check the task history: if the run shows as stopped by a filter, the trigger fired fine. Filters are strict about exact text, capitalisation and empty fields — a trailing space is enough.

5. The connection expired

Password changes, revoked access and expired tokens silently break connections. Reconnect the app from the connections list, then re-test.

6. You're out of tasks

When the monthly task limit is hit, Zaps stop and the reason is easy to miss. Check usage before assuming a logic problem.

7. The trigger is watching the wrong place

Wrong spreadsheet tab, wrong folder, wrong pipeline, wrong form. Re-open the trigger step and confirm every dropdown, not just the app.

How to find it faster next time

1. Open the task history first — it tells you whether the trigger fired at all.
2. If it fired: the problem is a filter, a mapping or the action.
3. If it didn't: the problem is the trigger, the connection or the data you used to test.