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.

How it Currently Works:

----------------------------------------

Zocuments API expects a dictionary for document merge data. In Zapier I've had to implement 2 input fields to associate dictionary keys (merge keys w/in the document template) and values (cells from a Google Sheet) to accomplish the build up of this dictionary.

imageedit_3_5923722378.gif

In the above screen shot, the Template Key Search input is populated by a Trigger so the user can copy/paste into the Template Merge Field Data key:

Screenshot from 2019-10-08 10-38-04.pngUser must copy/paste from Template Key Search into left-hand key side of Template Merge Field Data. And repeat the process for as many key/value pairs needed.

Screenshot from 2019-10-08 10-38-44.png

This is somewhat cumbersome for the end-user to figure out, and requires lots of clicking/copying/pasting back and forth.




Proposed Alternative:

----------------------------------------

I would like to propose the key side of the dictionary inputs can also be populated w/ a Trigger just like the value side is

imageedit_7_8976329177.png

This would reduce the number of inputs, drastically decreases the click count, and would make for a better overall end-user experience.


Thoughts?


@Zocuments - I like your thinking! On a similar vein, it would be nice if both sides of a filter rule could be populated variably unlike now.

FYI, official Zapier policy is for all requests to goto contact@zapier.com so they can be probperly logged (although it's still fine to discuss them here).

However, this one sounds like it might involve changes to the integration builder platform - so maybe requests for that get differently routed, I'm not sure? @Danvers / @jesse will probably jump in here at some point to clarify.


Hey @Zocuments! Thanks for the thoughtful feedback about the Zapier app builder!

@Andrew_Luhhu is right that the best thing to do if you have some feedback or a feature request is to drop the support team a line - this is true of the development platform as well. I've forwarded this message to the team to save you from having to type out your thoughts again, they'll be in touch as soon as possible 🙂

Of course you are more than welcome to discuss your thoughts about things like this on the Community, it can be great to bounce ideas of other people and we definitely don't want to stop you from doing that!


Terms & Conditions