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

This will be the title of the Card as you see it on your Board. Digital Assistant will create the Card automatically. Or if you want to add this Zap *to an existing* Card, just match the name with the already existing Card.

### Let's fill your Card with life
Each time this Zap gets triggered your Card will gain a new item. In the *below* section we're going to map fields from your Trigger to correspond to each field in the list.

This will be the main headline for each item, e.g. the title of a news article or the name of a task

If your Trigger provides an image URL, e.g. from a news article, you can select it here and the Card will display it

If your Trigger provides a description, e.g. an excerpt from an article or the description of an issue, this will be shown underneath the title

If your Trigger provides a create time, select it here. This will show beneath the description of the item.

If your Trigger provides a direct link, select it's URL here. This will show users an 'Open' button that sends the them to the original item.

Enter an emoji that will be shown next to the item to indicate its status. For example, you can use '🟢' for positive events, and '🔴' for negative ones.

If true, then each item can be removed by the user by clicking a '✕' icon

Will show this Card only to the selected roles. Manage roles within the Digital Assistant settings.

### Optional: Make the Card actionable for the user

The *below* section can be used for Triggers that require some kind of response from the user, for example for tasks, tickets or failure reports.

Skip this section, if you just want your Card to be a feed.

If your Trigger provides a due date, e.g. a task deadline, you can enter it here and the Card will show it

If your Trigger provides the email address of the assigned user, select it here. If it matches with the email of a Digital Assistant user, then only they will see the item.

true/false. Improves notification behavior of Digital Assistant. Enter 'true' if the user should decide whether the item needs a reaction (e.g. a server stopped responding, new ticket created), or 'false' if it's more informational (e.g. deploy succeeded, ticket has been closed).

Assign the item a unique ID by selecting a suitable attribute from your Trigger

Freely define extra pairs of field names and values that can be used to further customize your Adaptive Card (by going to the Designer tool)

Viva Connections is a dashboard for Microsoft SharePoint that transforms your Zaps into Cards that aggregate triggers as convenient lists.

Viva Connections

Whenever a new webhook is caught, this Zapier template will add a corresponding entry to your Adaptive Card list on your adenin dashboard.

Viva Connections + Webhooks by Zapier

Generate Viva Connections entries from new incoming webhooks

Supported triggers and actions

Catch Raw Hook

Retrieve Poll

GET

PUT

Catch Hook

Custom Request

POST

Generate New Card Entry

About Viva Connections

Related categories

About Webhooks by Zapier

Related categories