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

The name of the application, found in the newrelic.yml file.

The name of the user/process that triggered this deployment

Text annotation for the deployment — notes for you

The revision number from your source control system (SVN, git, etc.)	

New Relic provides SaaS Application Performance Management for Ruby, PHP, .Net, Java, Python, Node.js, Android, and iOS Apps.

New Relic

Pingdom website monitoring reports the uptime, downtime and performance of your website, network and server and alerts you of errors.

Pingdom

StatusCake checks your website for uptime and performance

StatusCake

In an always-on world, teams trust PagerDuty to help them deliver a perfect digital experience to their customers, every time. PagerDuty is the central nervous system for a company's digital operations. PagerDuty identifies issues and opportunities in real time and brings together the right people to respond to problems faster and prevent them in the future. From digital disruptors to Fortune 500 companies, over 12,000 businesses rely on PagerDuty to help them continually improve their digital operations-so their teams can spend less time reacting to incidents and more time building for the future.

PagerDuty

Amazon CloudWatch is a monitoring service for AWS cloud resources and the applications you run on AWS.

Amazon CloudWatch

With Zapier's Webhooks integration you can integrate to any app that supports webhooks. By adding a Zapier webhook URL to that app you can automatically receive a POST request when certain things happen in the app. 

Then, with this integration, Zapier can use the request data to automatically set up a deployment in New Relic, ready for monitoring.
Once you have set up this integration, a new deployment will be created automatically when the Webhook is triggered.

A Webhook post request is received from a source app

Zapier creates a New Relic deployment record with details from the request

New Relic + Webhooks by Zapier

Create New Relic deployments from a Webhook

Supported triggers and actions

Catch Raw Hook

Retrieve Poll

GET

PUT

New Deployment

Catch Hook

Custom Request

POST

New Alert or Deployment

About New Relic

Related categories

Similar apps

Pingdom

StatusCake

PagerDuty

About Webhooks by Zapier

Related categories

Related Zap Templates

Related Zap Templates