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 have a Webhook that I using to POST to an API via JSON.  When I plug in my data, if any of the fields happen to be empty (which is valid), there is a value that looks like an ID being populated in those fields.  I don’t why that is happening and how to fix it.  Below is an example of the JSON output and a snippet of the JSON in the Setup Action section where I am building the JSON string.

 

  



 

"firstName": "Richard",

"addressExtn": "aXJVuaPhUBvexU44GFd_UP",

"dateOfBirth": "1962-01-08",

Thanks,

Rhonda

Hi @RBailey 

Might be best to open a ticket with Zapier Support for further assistance with this one: https://zapier.com/app/get-help

Hi friends! I wanted to pop in and share some of the details from the support ticket that may be helpful.

It turns out there was a step in the zap where data pass through was turned to true - in this scenario it needed to be set to false. I’ll share context below:

If the Data-Pass through field is set to yes, the request data that's used will be overridden with the raw data from the previous step. This means that a possible use case for using this function would dynamically pass the raw data from a previous code step, or webhook through this custom webhook step.
 
Another possibility could be that in a previous step both the raw data and formatted data is received, but the way the raw data was formatted is difficult to parse out or map. This function allows the raw data to fill in the request, and then you would only have to apply the appropriate headers in the “Headers” fields below.
 
This Youtube video, while not directly addressing this kind of thing alludes to this same situation where the raw data is of better use than how the data is formatted once received.

I hope this is useful!

Terms & Conditions