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.

The documentation for setting up Dictionary type inputs in the Zapier CLI does not seem to provide how to implement them with the other inputs for Field mapping. I am receiving errors when attempting to set up and test the dictionary field in my Zap. Any examples of an active Dictionary input set up in the CLI/Clarifying documentation would be greatly appreciated.  

Hi @RobertPRollick - Dictionary input fields are basically Key-Value pairs of strings. When building with the CLI, they can be configured by adding dict: true to your input field configuration.

For example:

{
  "key": "metadata",
  "Label": "Metadata",
  "dict": true
}

In this example, you can reference this as bundle.inputData.metadata. which will give you an object of key-value pairs. Both the keys and the values are strings.

@ikbelkirasan I understand that but it looks like if the dictionary type is set up through the UI, that multiple fields can be added as needed by whoever is using the zap https://platform.zapier.com/docs/input-designer (talking about the + sign in the dictionary section). Whereas when I set this up in the CLI it is only capable of setting up one field that I have to supply the key and Label for. 

@RobertPRollick - That’s strange and I’m not sure why you’re seeing this behavior. I went ahead and tested with the CLI adding that metadata input field I mentioned above and here’s what I got. Seems to be working as expected. So, can you show me what your dictionary field configuration looks like? 

 

 

@ikbelkirasan I had the dict attribute before the key and label. Looks like that was causing the issue. Is there documentation on how to parse through the collected pairs or does it act as an associative array? 

@RobertPRollick - The collected pairs are provided to the handler function as a JavaScript Object.

For example:

bundle.inputData.metadata value would be:

{
  "key1": "value1",
  "key2": "value2"
}

 

@ikbelkirasan Thank you for your quick response!

Reply


Terms & Conditions