Skip to main content
Question

Troubleshooting data retrieval from Google Sheets in Zapier


Hi, 

I’m pulling a sheet from a shared drive. When a new row is added it should trigger a message into slack. The sheet is made up of google form submissions rather than straight forward text but was previously pulling all data through to zapier. Now when I try to test the records, I can see the column headers, but no data found. there are no errors in the active sheet 

Did this topic help you find an answer to your question?

2 replies

JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 2259 replies
  • January 14, 2025

Hi ​@Ops1234,

 

Welcome to the Community.

 

If your Google Sheets to Slack Zap isn't working, ensure the trigger is set to "New Spreadsheet Row" with the correct spreadsheet and worksheet selected. Verify that sheet data is complete and valid, and check the sharing settings to confirm that Zapier has access. Reconnect Google Sheets to Zapier to resolve potential connection issues. Test the Zap after these steps, and if it still fails, the issue may involve the Google Sheets API. Sharing detailed information about your Zap's setup can help identify a solution. Obscure any sensitive information within the screenshot for security purposes. 

 

Thank you.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7396 replies
  • February 19, 2025

Hey there, ​@Ops1234 👋

Did you manage to get this sorted by reconnecting the Google Sheets account and double-checking the settings as Jammer suggested?

If not, as you’re using a Google Sheets spreadsheet on a shared drive, it could be that you need to use the Team Drive version of the New Spreadsheet Row trigger:

a8e3087e826a8fcbedaf35e13c950467.png

Alternatively, were there any structural changes made to the spreadsheet after it was connected to the Zap?

If so, I’d recommend turning the Zap off and on again to reset the connection to the spreadsheet. See our Google Sheets error: Zap not triggering guide for more details.

Hope that helps. If you fixed it a different way or have run into any more issues, just let us know! 🙂