New Relic

Monitor applications, query metrics, and manage alerts with the New Relic API.

Detail	Value
Category	Monitoring
Base URL	https://api.newrelic.com/v2
Authentication	API Key
Endpoints	8
Connector key	newrelic

Using New Relic in a workflow

1. Go to Connections and click New Connection.
2. Pick New Relic from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /applications.json	List applications
GET /applications/{id}.json	Get application details
GET /applications/{application_id}/metrics/data.json	Get metric data
GET /alerts_policies.json	List alert policies
POST /alerts_policies.json	Create an alert policy
GET /alerts_violations.json	List alert violations
GET /alerts_incidents.json	List alert incidents
GET /key_transactions.json	List key transactions

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /applications.json

List applications

Detail	Value
Operation ID	monitoring.listApplications
Method	GET
Path	/applications.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listApplications.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

GET /applications/{id}.json

Get application details

Detail	Value
Operation ID	monitoring.getApplication
Method	GET
Path	/applications/{id}.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.getApplication.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

GET /applications/{application_id}/metrics/data.json

Get metric data

Detail	Value
Operation ID	monitoring.getMetricData
Method	GET
Path	/applications/{application_id}/metrics/data.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.getMetricData.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

GET /alerts_policies.json

List alert policies

Detail	Value
Operation ID	monitoring.listAlertPolicies
Method	GET
Path	/alerts_policies.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listAlertPolicies.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

POST /alerts_policies.json

Create an alert policy

Detail	Value
Operation ID	monitoring.createAlertPolicy
Method	POST
Path	/alerts_policies.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.createAlertPolicy.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

GET /alerts_violations.json

List alert violations

Detail	Value
Operation ID	monitoring.listAlertViolations
Method	GET
Path	/alerts_violations.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listAlertViolations.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

GET /alerts_incidents.json

List alert incidents

Detail	Value
Operation ID	monitoring.listAlertIncidents
Method	GET
Path	/alerts_incidents.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listAlertIncidents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.

GET /key_transactions.json

List key transactions

Detail	Value
Operation ID	monitoring.listKeyTransactions
Method	GET
Path	/key_transactions.json

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your New Relic connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listKeyTransactions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream New Relic API reference.