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.

Hi,

I am new to zapier. I am trying to create an Action in which I want to take different inputs which are part of my API. I am able to add flat structure inputs (like: name:{}, age:{} ...). But I am facing problem to create input fields for complex json formats like:

“items”: 
    {
        "number": "1",
        "quantity": 1,
        "amount": 100,
        "taxCode": "PS081282",
        "itemCode": "Y0001",
        "description": "Yarn"
    }
],

"addresses": {
    "currentAddress": {
        "line1": "1-224, min street",
        "city": "Irvine",
        "region": "CA",
        "country": "US",
        "postalCode": "55423"
    }
}

 

Please help me to know how I can create input fields for “items” and “addresses”.

You can use the children array to create “line items” if your users will be mapping in data that will be passed in as an array from a trigger step or a subsequent action.  For your ‘items’ object this seems like a rational approach.  https://zapier.github.io/zapier-platform-schema/build/schema.html#fieldschema

If you wanted to have a user explicitly map zero-or-many, discrete, complex objects - say if the input bundle had two named address objects - there’s not a great way to do this today unfortunately.

The other option is to explicitly create the input fields as a “flat set” and then shape that data how your API expects it, in code, before Zapier posts it.  Probably the best approach for your address object.  

Hopefully that made sense.  If not let us know and we can point you to some examples to better illustrate.  

Terms & Conditions