Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Zapier had trouble retrieving custom fields from Google Docs.

  • June 17, 2020
  • 1 reply
  • 257 views
A

Hi! I received this message in my Create Document from Template step in Google Docs. It happens only when I use a custom value for the ID of the doc. If I specify a Template Document, it works fine!

 

Is it possible to retrieve fields using a custom value for the ID of the doc?

 

Thanks

Best answer by nicksimard

Hi @aclmelo2!

I looked into this for you, and I see an existing bug report about this particular issue. I’ve added you as an affected user, so when it gets resolved you’ll be notified via email. To be fully transparent I believe this is a limitation of the Zap editor/the Google API, so I’m not sure how soon it will be possible.

Luckily, there may still be a way to work around this. As long as (a) the document template already exists and (b) the custom fields are the same, you can:

  1. Make a selection from the drop-down menu options
  2. The fields should then appear - map these fields out
  3. Revert the Template Document field to a custom value selection

This will throw you a warning that the custom fields are now extra (or something to that effect). Ignore that warning and click "Continue" and test the step out.

NOTE: this workaround can be finicky, but I figured I’d offer it in case you want to try it out.

View original
Did this topic help you find an answer to your question?
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

nicksimard
Forum|alt.badge.img+11
  • nicksimardZapier Staff
  • Zapier Staff
  • 2115 replies
  • Answer
  • June 18, 2020

Hi @aclmelo2!

I looked into this for you, and I see an existing bug report about this particular issue. I’ve added you as an affected user, so when it gets resolved you’ll be notified via email. To be fully transparent I believe this is a limitation of the Zap editor/the Google API, so I’m not sure how soon it will be possible.

Luckily, there may still be a way to work around this. As long as (a) the document template already exists and (b) the custom fields are the same, you can:

  1. Make a selection from the drop-down menu options
  2. The fields should then appear - map these fields out
  3. Revert the Template Document field to a custom value selection

This will throw you a warning that the custom fields are now extra (or something to that effect). Ignore that warning and click "Continue" and test the step out.

NOTE: this workaround can be finicky, but I figured I’d offer it in case you want to try it out.

Terms & Conditions