Send webhooks in Zaps

• In the Zap editor, click the plus + icon to add an action step.
• Search for and select Webhooks by Zapier.
• Click the Action Event dropdown menu and select a webhook option.

Webhooks by Zapier offers GET, POST, PUT methods, which include automatic data parsing, and you can also select Custom Request for other use cases.

Use GET if you want the step to retrieve information from a server. Use the POST or PUT methods if you’re sending files (file objects cannot be sent via Custom Request), or if you're not comfortable writing JSON or XML and would prefer the Zap to parse the information for you.

The app also offers a Custom Request option. This option offers more flexibility and allows you to type out JSON or XML, but is also much less forgiving. Unlike the POST, PUT, and GET methods, it does not automatically parse information for you.

Use Custom Request if your use case involves the following:

• The PATCH or DELETE HTTP methods.
• Sending a nested JSON array.
• Sending empty values.
• Extremely customized headers.

After you've selected the webhook option, click Continue.

To make sure the request is sent in the way your app expects, select the correct format from the Payload Type dropdown menu.

There are three common serialization formats that you will see listed here: Form (also called URL-encoded), JSON, and XML. The following are examples of each format:

Form

first_name=Bryan&last_name=Helmig&age=27

JSON

{
  "first_name": "Bryan",
   "last_name": "Helmig",
   "age": 27
}

XML

<first_name>Bryan</first_name>
<last_name>Helmig</last_name>
<age>27</age>

You can also select Raw to send the request as-is. With this option, no data fields will be parsed.

In the URL field, enter the URL where your app’s API is able to receive requests.

It's recommended not to add URL parameters in this field. Instead, enter URL parameters in the Data fields.

Fill out the Data section. If you’re using a templated action like PUT, POST*, or GET (i.e. not a Custom Request), enter the key for the field on the left side, and the field value on the right. Data from previous steps can be used in the value field, and you can click the plus icon +** to add more parameters if needed.

If you need to add nested values, you can define child objects by adding the parent object and a double underscore before the object. Below is an example of what this looks like when entered into the Data section. The | (pipe) symbol is used only to separate what goes in the left-side and the right-side fields, and doesn't need to be added to the Zap.

order | value
item__price | value
item__sku | value

That will turn into JSON that looks like this:

{"product": "value", "item": {"price": "value", "sku": "value"}}

For more detailed nesting, use the Custom Request action.

Using the Custom Request action

If you’re using Custom Request, type raw JSON (or other formats) directly into the Data field. Zapier will not parse or format this data for you and it will be sent exactly as entered, so it's recommended to use a JSON (or other) validator to verify that the syntax is correct.

You can send specific headers by filling the fields in the Headers section.

You can also set up basic authentication (involving just a username and password, or username and API key) using the Basic Auth field.