Best answer

New task in Asana to Google Sheets

  • 1 December 2021
  • 5 replies

  • Anonymous
  • 0 replies

Hi there!


We’ve been using Zapier for a quite some time for transferring data from Asana to Google Sheets. The process is simple. We’ve got several projects: one project for one legal entity. We also configured two ZAPs fro each project:

  1. New Row - this Zap adds a new row to a Google Sheet when there is a new task added to the project
  2. Update Row - this Zap takes ID of the task, looks through the column with IDs on a specific Google Sheet (the one, where first Zap pastes the data), identifies required row and updates it every time the task itself is being updated. 

The process is very simple and straightforward. Today for some reason all our “New row” tasks for 5 projects stopped working all at once. At the same time we literally did not change a thing!


In order to fix the problem we tired the following:

  1. Log out and log in: Zapier, Asana, Gmail
  2. Test trigger and test action for each “New row” Zap - everything works fine. Trigger says “we found a task!” and Action successfully adds a new row to the spreadsheet. But when we just add a task in Asana as we used to - nothing happens. Google Sheet remains unchanged.
  3. We tried to test connection of our Zapier account with Asana and Google Sheets and reconnect as well. Did not help.
  4. We created a new Zap and a new Google Sheet in order to check whether they are going to work or not. Situation is the same as in p.2. Everything seems fine but does not work.

Interesting thing is that “Update row” works perfectly fine. At the same time it keeps saying that there is a mistake since this Zap tries to update a row, but can’t find via ID it since a task with this ID has not been added to the spreadsheet yet.

We do not know what to do. These Zaps are crucial for our business processes. Please help!


Best answer by Troy Tessalone 1 December 2021, 18:49

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies


Userlevel 7
Badge +14

Hi @Vitaliy Makarov

You may need to remap the Zap step that is having the error.

Check if the GSheet had any changes by looking at the version history log in the GSheet:

Check the available GSheet Zap help articles:


If you still need help, try opening a ticket with Zapier Support:

Hi @Troy Tessalone,


Could you please clarify what do you mean by remapping the Zap step?

The thing is “New row” Zap does not have an error. It is just not triggered upon adding of a new task, however, it is supposed to be triggered.

Userlevel 7
Badge +14

@Vitaliy Makarov 

Could you please clarify what do you mean by remapping the Zap step?

Try reselecting the options and remapping the variables in the GSheets Lookup Row step.

Userlevel 7
Badge +14

@Vitaliy Makarov

The Google Sheets trigger on my Zap stopped working

If your Google Sheets trigger stops working suddenly, first check if you’ve accidentally inserted a blank row anywhere in the spreadsheet. Zapier interprets a blank row as the end of the spreadsheet and may have trouble finding any new rows below it.

In addition to this, making the following changes to your spreadsheet while the Zap is turned on can cause errors:

  • Deleting existing rows or columns.
  • Adding rows anywhere other than to the bottom of your sheet.
  • Resorting the sheet.
  • Renaming/adding/rearranging columns.
  • Renaming the sheet.
  • Filtering the sheet.

If you need to make any of those changes to your Google Sheet, turn your Zap off while you work on the spreadsheet, and then turn it back on again.


The Google Sheets trigger is marked "instant" but it still takes a few minutes to trigger

The triggers for Google Sheets are unique among Zapier triggers. When there is a trigger event in the spreadsheet, Zapier gets a notification webhook from Google about this. After that, Zapier sends Google Sheets a request for new data, so it uses both the polling and instant trigger methods. This process takes about 3 minutes overall.

While not being "instant", these triggers are faster than regular polling ones, as they don't depend on the polling interval of the plan your account uses.