Short answer
Why Is My Zap Not Triggering?
A Zap usually does not trigger because it is off or unpublished, the trigger is polling and has not checked yet, the source event does not match the selected trigger, or Zapier has already seen the item. Confirm the Zap is on, create a brand-new qualifying test item, wait one polling interval, and inspect Zap History before reconnecting the source app.
Common causes
- The Zap is off, paused after repeated errors, or has unpublished edits.
- A polling trigger has not reached its next check, while an instant trigger is not receiving its webhook.
- The source item is old, in the wrong view or status, or missing a required field.
- Zapier recognizes the item ID and suppresses it as a duplicate.
- A filter or path stops the run even though the trigger succeeded.
- The app connection is expired, revoked, or connected to the wrong workspace.
Diagnostic steps
- Open the Zap and verify that its current version is published and switched on.
- Create a genuinely new source item that meets every trigger condition; do not reuse the editor sample.
- Wait at least one full polling interval when the trigger is not marked instant.
- Open Zap History and search around the event time. A filtered run means the trigger worked.
- Test the trigger connection, then confirm account, workspace, folder, view, and status selections.
- Check the source app and Zapier status pages before changing a previously working configuration.
Example
A “New Spreadsheet Row” Zap will not fire when you edit an existing row used during setup. Add a fresh row beneath the current data range, wait for the polling window, and then inspect Zap History. If a run says “Filtered,” troubleshoot the filter rather than the trigger.
Caveats
Polling frequency varies by Zapier plan and integration. Some apps define “new” only after an item reaches a particular state. Replaying or duplicating business actions can create real customer-facing side effects, so use a test workspace or reversible record where possible.