Zapier Google Sheets Trigger Not Firing on New Rows
Short answer: Zapier does not get notified the instant a row appears. It checks the sheet on a schedule set by your plan, compares what it finds with what it saw last time, and only then fires. Zaps miss rows when the header row changes, blank rows sit in the middle of the data, rows are produced by formulas like IMPORTRANGE or QUERY, rows are inserted rather than added at the bottom, or the trigger column used by "New or Updated Spreadsheet Row" never changes. Clean up the sheet structure, add rows at the bottom with real values, choose the right trigger and column, then test with a fresh copy of the sheet.
How the trigger actually works
The Google Sheets triggers in Zapier are polling triggers. On each check, Zapier reads the sheet and looks for rows it has not processed before. How often it checks depends on your Zapier plan; the Google Sheets help on Zapier explains the trigger behaviour and common issues.
This has two practical consequences:
- A short delay is normal. If your Zap runs a few minutes after a row appears, nothing is broken.
- Zapier only sees what is stored in the sheet. If a value is calculated on the fly or the layout shifts, Zapier may miss or misread rows.
Before changing anything, open the Zap's history and check whether runs were skipped, filtered, errored or simply never happened. A Zap that is off, or that stopped after repeated errors, looks the same as a broken trigger from the outside.
Cause 1: Header row changes
Zapier uses row 1 as the column headers and maps fields by them. Problems start when someone:
- Renames a column, for example "Phone" becomes "Mobile"
- Inserts a new column between existing ones
- Leaves a header blank
- Adds a title or logo row above the headers
Keep a single header row in row 1, with a unique name in every used column. After any structural change, open the Zap, refresh the fields in the trigger step and re-map them in later steps.
Cause 2: Blank rows and inserted rows
"New Spreadsheet Row" is designed for rows added to the bottom of the data. Watch for:
- Blank rows in the middle: someone leaves an empty row as a visual separator. Zapier may treat the data as ending there.
- Rows inserted above existing ones: sorting the sheet, or inserting a row at the top so new entries appear first, confuses which rows are new.
- Deleted rows: clearing old rows can shift positions so Zapier thinks it has already seen the new ones.
If people like a sorted view, keep the raw sheet untouched and use a separate tab with a filter or sort formula for reading.
Cause 3: Rows created by formulas or imports
This is the most common reason for "the row is there but nothing happens". When a tab is filled by IMPORTRANGE, QUERY, FILTER, ARRAYFORMULA or a connected data source, the cells hold formulas that recalculate, not plain values written into new rows. Zapier often does not detect these as new rows, or sees them change unpredictably.
Fixes, in order of preference:
- Trigger on the source instead. If rows come from a form, trigger the Zap on the form submission itself rather than on the sheet.
- Write real values. Have the upstream tool append rows as values, for example a Zapier "Create Spreadsheet Row" action or a form's native sheet connection, which writes values.
- Copy values with a script. A small Apps Script on a schedule can copy new results from the formula tab to a plain tab that Zapier watches.
Rows pasted in bulk can also behave differently from rows typed one by one, so test with the method your team actually uses.
Cause 4: The wrong trigger or trigger column
Zapier offers two main row triggers:
| Trigger | Fires when | Use it for |
|---|---|---|
| New Spreadsheet Row | A new row appears at the bottom | Simple append-only logs, form entries |
| New or Updated Spreadsheet Row | A chosen trigger column gets a new value | Rows that are filled in stages, or approval workflows |
With "New or Updated Spreadsheet Row", Zapier watches only the trigger column you pick. If you choose a column that is filled in when the row is created and never changes, updates elsewhere in the row will not fire it. A good pattern is a dedicated column such as "Ready to send" that someone sets to "Yes" when the row is complete. That way the Zap does not fire on a half-filled row.
Also note the "Any column" option for that trigger, which can fire more often than expected, including on small edits.
Cause 5: Permissions, shared drives and the connected account
- The Google account connected in Zapier must have access to the sheet. If the file was moved, its owner changed, or sharing was removed, the trigger quietly finds nothing.
- Files in shared drives may need the shared drive selected explicitly in the trigger setup.
- If the connection was reauthorised with a different Google account, the Zap may now look at a sheet that account cannot open.
Check the connection under My apps in Zapier and confirm the email shown there can open the sheet in a browser.
Test with a clean sheet
When nothing obvious stands out, isolate the problem:
- Make a new spreadsheet with a single header row copied from the original.
- Point a copy of the Zap at it.
- Type a row of plain values at the bottom.
- Wait for the next polling check, or use the Zap editor's test step to pull in the latest row.
If the clean sheet works, the original sheet's structure is the issue, and you can compare the two. If the clean sheet also fails, look at the Zap settings, connection or plan.
FAQ
Why is there a delay before the Zap runs?
The trigger polls on a schedule set by your plan. A few minutes' wait is expected behaviour, not a fault.
Can Zapier detect rows added by IMPORTRANGE?
Not reliably. Trigger on the original source, or copy the imported rows into a values-only tab that Zapier watches.
Should we sort the sheet Zapier watches?
No. Sorting moves rows around and confuses which are new. Use a separate tab for sorted views.
What is the best trigger column to choose?
A column that is set only when the row is complete, such as a status or "Ready" column.
Sheet-based automations that keep missing rows can be made dependable, and we are happy to rebuild yours.