By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given `{"contact": {"name": "Mike"}}`, add "contact" here to only return `{"name": "Mike"}`. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: `[{"id":1234},{"id":1235}]`

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the `id` key. If the `id` key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with `id` in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (`|`) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request `data` below will be overridden with the raw data from the previous step (you are still responsible for headers though, like `Content-Type`). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data `Content-Type`. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

Returns the raw response from the request, in the following keys: response, status, headers. Ignores `Unflatten`.

We recommend *not* putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. *Note:* If you specify nothing for this field, **we will automatically encode and include every field** from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the **Custom Request** action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to `multipart/form-data`, with the above payload type defining the sub content-type for the data being passed.

Webhooks simply POST data (or JSON) to a specific URL every time we see something new. Webhooks can also accept data (or JSON) to kick off a workflow in Zapier.

Webhooks by Zapier

A unique identifier for the person. This is usually the user id generated when an account is created with your product or service. If such an id doesn't exist, set this to an email address, instead.

The person's email address. This field is optional, but recommended when creating a new person in your Customer.io account.

Add any attributes which would be useful. e.g. Name: John Doe.

The name of the anonymous event you want to track. Learn about anonymous events [here](https://customer.io/docs/anonymous-events/).

The unique id the event will be stored against. Learn more [here](https://customer.io/docs/anonymous-events/#api-anonymous-events).

Any related information you’d like to attach to this anonymous event.

Any related information you’d like to attach to this event.

With Customer.io you can send email, SMS, and push based on what people do or don't do in your app.

Customer.io

ActiveCampaign is a customer experience automation (CXA) platform that helps businesses meaningfully engage customers. Access pre-built automations that combine transactional email and email marketing, marketing automation, ecommerce marketing, and CRM for powerful segmentation and personalization across social, email, messaging, chat, and text.

ActiveCampaign

Automate your ecommerce marketing at scale. Drip is your ecommerce marketing engine. Build personalized customer experiences, drive more revenue, and take your marketing strategy to the next level with Drip.

Drip

Kit is an email marketing platform for professional bloggers. Easily create email sequences, tag subscribers, grow your list, and automate your email marketing.

Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses grow.

Brevo

Instantly build dynamic interfaces that connect to Zaps and a data source (like Tables). Interfaces gives you a drag-and-drop way to build visual workflows for any business process, without writing code.

Zapier Interfaces

This integration creates customers in Customer.io from newly caught webhooks.

Customer.io + Webhooks by Zapier

Create customers in Customer.io from newly caught webhooks

Supported triggers and actions

Catch Raw Hook

Retrieve Poll

GET

PUT

Create Anonymous Event

Catch Hook

Custom Request

POST

Create or Update a Person

Create Event

About Customer.io

Related categories

Similar apps

ActiveCampaign

Drip

Kit

About Webhooks by Zapier

Related categories