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.

I need to send this from Zapier (see “parameters” field)

{
  "account": "5698227xxxx",
  "name": "requerimiento_1",
  "parameters": t"Francisco"],
  "phone": "5699349xxxx"
}

 

But Zapier sends this

{  "account": "5698227xxxx",  "name": "requerimiento_1",  "parameters": "Francisco",  "phone": "5699349xxxx"}

 

I tried to use nested parameters (with the double underscore) and got this

{  "account": "5698227xxxx",  "name": "requerimiento_1",  "parameters": {    "": "Francisco"  },  "phone": "5699349xxxx"}

 

Help!! 

Thanks!!!

Hi @fromero 

Can you please further elaborate on your use case?

Are you getting an error from the receiving app?

Just wanted to follow up here for anyone also running into similar issues here to mention that in order to send a nested array the Custom Request action would need to selected for the Webhooks by Zapier app.

 

If that action is selected and it’s still altering the format when double underscores are used, then it could be that the Unflatten option needs to be set to No. By default it will automatically try to convert fields with double underscores so that may be why it’s being altered:
398fbe9cc1facdfbc943da29aa1faf7a.png

If that doesn’t do the trick, it may be worth using a JSON validator like JSONLint to check its valid. And we have some helpful guides and resources that may be useful in troubleshooting further:

Terms & Conditions