Skip to main content

This seems like such a simple request, but ive wasted sooo much time trying to get it to work!

There is a trigger for Google Sheets that seems fine:
"New or Updated Spreadsheet Row (Team Drive)” - if a new row appears in the Google Sheet OR if an existing row/record is updated in that Google Sheet.

The annoying problem is the Action does not exist to handle both. You can either choose the Action: “Create new record” or “Update Record”. If I set the action as “Create Record”, then in the case where an existing record is modified in Google Sheets, instead of modifying that record in Zapier Tables, it will just create a whole new row in the zapier table.

Even if i goto the trouble of making 2 separate Zaps for the 2 separate acitons (one for new records, one for updating) there is not 2 separate Triggers for Google Sheets (only the combined trigger for new or updated row).

I dont understand why Zapier Tables wouldnt be coded out of the box to be able to integrate with Google Sheets. Seems like a very common requirement????

Has anyone managed to just keep a simple automatic sync working between these 2 that can share the steps?

 

(hopefully something more helpful than just posting these 2 links below like ive seen throughout this community forum, thanks!)

GSheetshttps://zapier.com/apps/google-sheets/integrations#triggers-and-actions

Zapier Tableshttps://zapier.com/apps/zapier-tables/integrations#triggers-and-actions

Hi ​@ren55, welcome to the Community! 🎉

You might want to look at using Paths by Zapier for this. With Paths you’d have a Find Record action to search for a record (that matches whatever unique identifier you’re using to match the details between the spreadsheet and table) and have two paths to carry out actions accordingly:

  • Path A would run if an existing record wasn’t found, which would indicate that the Zap triggered for a new spreadsheet row. In that path you’d have a Create Record action.
  • Path B would run if an existing record was found, which would indicate that the Zap triggered for an updated spreadsheet row. In that path you’d have an Update Record action.

That way the Zap would only create a new record for new rows and update existing records for when there’s an update in the spreadsheet. If you’ve not used Paths in Zaps before I’d recommend checking out our Add branching logic to Zaps with paths guide to get started.

Can you give that approach a try and let me know if that does the trick?


​Hey there, ​@ren55👋

How are things going on this? Were you able to get it sorted using Paths, or did you find an alternative solution?

Looking forward to hearing from you! 🙂


Thank you for trying to assist me with this Sam.

I ended up using make.com and was able to achieve my end result

Have a good day

R


Thanks for the update, @ren55. I’m really glad to hear you were able to get a solution in place—even if it wasn’t with Zapier this time!

If you ever decide to revisit this workflow or need help exploring other use cases with Zapier in the future, feel free to reach back out. We’re always happy to help.

Wishing you a good day as well! 🤗