Skip to main content
Question

Zap works during testing but doesn't run automatically — what am I missing?

  • Nov 20, 2026 12:41 PM UTC
  • 2 replies
  • 9 views

Hey everyone!

I'm fairly new to Zapier and trying to figure something out.

I've set up a simple automation where every time a new row is added to Google Sheets, it should send a notification to Slack.

The weird thing is that when I test the Zap manually, everything works fine. But when I actually add a new row to the sheet, nothing happens.

I've checked that the Zap is published and turned on, and I don't see any errors in Zap History.

Am I missing something obvious here? Does Zapier take some time to detect new rows, or is there something specific I should check in the trigger settings?

Would really appreciate any suggestions from people who've dealt with this before!

Thanks!

2 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Nov 20, 2026 5:40 PM UTC

Huzaifa_ZP
  • Beginner
  • Nov 20, 2026 7:11 PM UTC

Hi kesilo8526, I've run into this a lot with client Sheets Zaps. Here's what I check, roughly in the order it usually turns out to be the cause.

1. Give it a few minutes. New Spreadsheet Row is a polling trigger, so Zapier checks the sheet on a timer, not the moment you type. On the Free plan that's every 15 minutes, paid plans check more often. A check that finds nothing new doesn't create anything in Zap History, so an empty history with no errors is normal while it waits.

2. Deleted test rows. This is the one that catches most people. Zapier remembers rows by row number, not by content. If you added row 12 while testing, deleted it, then typed a new row 12, Zapier thinks it already handled row 12 and skips it. It starts firing again once you go past the highest row number it has seen.

3. Where the row lands. Only rows added at the very bottom count. Inserting a row in the middle or sorting the sheet throws off the tracking. Renaming the spreadsheet or tab, adding or renaming columns after you set up the trigger, and frozen or hidden rows can break it too.

4. Which trigger you picked. If it's "New or Updated Spreadsheet Row" with a Trigger Column set, it only fires when that one column changes. Make sure it's a column you actually fill in on every new row.

5. Half empty Slack messages later on. Once it does fire, you might get messages with some fields blank. That happens when the poll catches the row after you filled the first cell but before the rest. Easy fix: use "New or Updated Spreadsheet Row" with the Trigger Column set to the last column you fill in, or paste the whole row in one go.

For a clean test: turn the Zap off, check the headers are in row 1, turn it back on, paste one complete row below everything else, wait 15 minutes and look at Zap History.

If it still doesn't show up, post a screenshot of the trigger step (spreadsheet, worksheet and trigger event) and I'll take a look.