Best answer

Can't pull Google worksheet data when looking up row after triggering from New Spreadsheet

  • 26 June 2020
  • 1 reply

Userlevel 1



Ultimate Goal

I’m trying to trigger sending a PDF of my google sheet (one worksheet or a group of specific worksheets) to a recipient that is defined in a row in my sheet, as well as the subject and the body of the email.

Our team utilizes a template that i’ve made to create new sheets, so I can’t attach zaps to this specific file, since they work on copies.

I already have a working script in my sheet that makes a copy of the sheet and puts it into a specific folder on our team drive, so I can trigger based on detecting a new sheet. (If there is a better way to trigger a zap on a template copy, and pull data from that specific copy every time, i’m open to suggestions)

The Zap So Far

I’m making the first step of this Zap “New Spreadsheet in Google Sheets.” It finds the sheet fine.

Do This … Lookup Spreadsheet Row. I can’t get this step to actually dig into the sheet that was found.  I always get the error “We’re having trouble loading 'Worksheet' data. The app returned "Requested entity was not found."

I’ve tried every line item under “Custom” since I want to pull the file data conditionally based on the first step, not just search the same test file every time.

What am I misunderstanding?


Pulls the file correctly
Can’t actually dig into the file



Best answer by Liz_Roberts 1 July 2020, 15:22

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.

1 reply

Userlevel 7
Badge +8

Hi @thartgrove86 ,

Thanks for reaching out- happy to help!

Currently, it is not possible to dynamically choose a spreadsheet in Google Sheets the same way you can dynamically choose options for other custom-value type dropdowns. This is because there isn’t a way for us to generate a good action template unless we know specifically which spreadsheet/worksheet combination will be used each time the Zap runs. 

However, check out this post for a workaround one of our Experts has shared! Let us know if that does the trick for you!