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.

When creating an Input Field that will have `children`, the children are displayed inside a little container/box under the parent. This is great.

 

The parent field still requires a `key` value, which I believe ends up being irrelevant / not used in the resulting `bundle.inputData`. This makes sense since the data gets mapped to the `key`s of each of the `children`.

 

However, the value that gets displayed for the surrounding box appears to come from the parent’s `key` and not the `label` property. Which seems unintuitive and less flexible to me.

 

Psuedo-code example:

{
  // This gets converted to Capital Case (or something) and used for display
  "key": "snake_case_key",
  // This does not get used at all...why not?
  "label": "Why don't you use me?",
  "children": e
    {
      "key": "child_one",
      "label": "I'm Child One",
      "type": "string"
    }
  ]
}

A screenshot that shows what I mean (not from that psuedo-code obviously):

 

This is correct, the Zap Editor uses the key as the display for line item groups, rather than label.

We’ll do better to document that.

Agree it’s not optimal. But it’s been working that way for so long now that if we just switched to using label, we’d likely see some surprising results where label never ended up getting tested. So it’d need to be a breaking change event, and we try to introduce those sparingly.

Side topic: Note that line item groups are meant for mapping input that you expect to be in an array. The platform will emit a corresponding array as output to your API. The emitted array will be named according to the key of the line item group. You’d mentioned

The parent field still requires a `key` value, which I believe ends up being irrelevant / not used in the resulting `bundle.inputData`.

So I wanted to point out that the key is significant when handling line item groups.

Terms & Conditions