Documentation for The Dictionary Inputs

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? 

@ikbelkirasan Thank you for your quick response!