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:
- Make a selection from the drop-down menu options
- The fields should then appear - map these fields out
- 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.