"Google Sheets: When a row is created" trigger no longer working?

Sorry, I don’t have a solution for you, but I just tested all of my Airtable automations that are triggered with “Google Sheets: When a row is created”, and they are all working just fine.

Here are some troubleshooting steps for you to try:

• In your Google Sheets spreadsheet, make sure that your “new row” is the very next empty row after the previous row that has data in it. In other words, make sure that there’s not an empty row in between the previous row and the next row.
• In your Airtable automation, re-test your trigger step, and then re-test your action steps after that.
• In Airtable, reconnect your Google Sheets connection.
• In Airtable, delete your Google Sheets connection and create a new one.
• Rebuild your automation entirely from scratch.

If you still can’t get it to work after all of that troubleshooting, then I would open a support ticket with support@airtable.com.

While you’re waiting for a response from them, you may want to quickly rebuild your automation using Make’s Google Sheets integrations in conjunction with Make’s Airtable integrations.

Make’s automations are infinitely more powerful than Airtable’s automations, so you may find lots of other uses for Make as well.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Hey ​@OP_55, 

Not having any issue on my side either! You’ll want to follow ​@ScottWorld’s exact walkthrough, and if the issue persists email support! -if that works, make sure to mark his answer as the best solution.

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel

Any chance you may have deleted a bunch of rows from that sheet recently?  I had some weirdness with the trigger after doing that

I'm having the same issue, did you find a solution? 

Hey, couldn't find any solution tbh, the problem was likely due to some degraded performance on my company Gsheets or Airtable, no idea, but after a few hours it went away, then came back the next day for a few hours. Haven’t seen the issue afterwards. 

Not quite a solution, but we ended up creating an alternative (manual) flow to process the stuff on the Gsheet, and then we added a script step that checks if there are current values, so that it doesn’t override anything.