Skip to main content

This is frustrating. So I need to make a POST request with a request body.

In the request body I need to have a ‘request’ paramter key and the value is a json.

The content type must be x-www-form-urlencoded. 

With the POST standard webhook, I cant choose the content type.

With the custom request webhook, it does not seems to recognize ‘request’ as a parameter in the request body. How can I solve this.

Hi @trung.nguyen 

For us to have more info, post screenshots showing how your Zap step is configured in EDIT mode.

Also, link to the API endpoint documentation you referenced to configure the Zap step.


Hi @trung.nguyen 👋

How are things going on this, were you since able to get this sorted?

If so, we’d love it if you can share some details on what the solution was - this would be super helpful to others that come across this thread in future! 🙏

And if not, with a POST action it looks like there’s an option to select the content type on the Payload field :

cb34c379d4d463c9dbabe3ee91cbf297.png
And for Custom Requests you’d have to specify that within the Headers section. For example:

a742e60398737f7453762badf2f53ead.png
 

You can learn more about how to send webhooks in a Zap here: Send webhooks in Zaps.

Hope that helps. Please do reach back out if you run into any further issues or questions! 🙂