Google Sheets: triggers unexpectedly or too soon

Symptoms

Your Zap runs, and as a result, subsequent steps of your Zap were missing or had incomplete information.
 

Cause

This can happen for two reasons:
  • New or Updated Spreadsheet Row trigger: You use this trigger in your Zap and have selected Any column to monitor. This means that any change to a row will trigger your Zap, even if it is a minor change, like a blank cell being filled in.
  • New Spreadsheet Row trigger: You use this trigger in your Zap, and Google Sheets is autosaving while still filling out a row. This can cause incomplete data to be sent to other steps in your Zap.

How to fix it

To resolve this issue, follow these steps:
  • Update the Trigger column. If you're using the New or Updated Spreadsheet Row trigger, select a specific column to monitor instead of Any. This will ensure that your Zap only triggers when there are changes to the column you have selected.
    • You can also add a column called "Send to Zap" to your spreadsheet. When you want the Zap to run, you can update that column.
  • Update the Google Sheet row at the same time. If you're using the New Spreadsheet Row trigger, try to enter data for the entire row at the same time. This will prevent Google Sheets from autosaving while you are still filling out the row.
    • If you can’t add data for the row at the same time, switch to using the New or Updated Spreadsheet trigger and specify a column that will trigger when the Zap runs.
miscEye icon Note
You can add a filter to avoid the Zap triggering on blank rows.
Was this article helpful?
1 out of 1 found this helpful