> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> Configure New Relic to send alert events into Rootly using a webhook notification channel with bearer token authentication, routing, and resolution sync.

## Introduction

New Relic can send alert events into Rootly as alerts using a webhook notification channel. Once alerts are flowing into Rootly, you can use alert workflows to create incidents, notify Slack channels, or page on-call targets.

With New Relic alerts in Rootly, you can:

* Receive New Relic issue events as Rootly alerts
* Filter and route alerts using workflow conditions on fields like `priority`, `state`, and `workflowName`
* Use alert workflows to automate incident creation and follow-up actions

## Before You Begin

Before configuring alert ingestion, make sure you have:

* The New Relic integration already installed in Rootly — see the [Installation](/integrations/new-relic/installation) page
* Access to configure notification channels or destinations in New Relic
* The bearer token from your Rootly New Relic integration settings

<Callout icon="triangle-exclamation" color="#FEF3C7">
  You must install the New Relic integration in Rootly before setting up the webhook. The bearer token is generated during installation and is required for authentication.
</Callout>

## Configure a Webhook in New Relic

<Steps>
  <Step title="Open notification channels in New Relic" icon="bell">
    In New Relic, navigate to **Alerts > Notification channels** and create a new channel.

    <Frame>
      <img alt="New Relic notification channels page" src="https://mintcdn.com/rootly/EZBU89ISF00990Wy/images/integrations/new-relic/alerts/images-1.webp?fit=max&auto=format&n=EZBU89ISF00990Wy&q=85&s=bf35fab664b61d8a1c036e205b901b6b" width="870" height="447" data-path="images/integrations/new-relic/alerts/images-1.webp" />
    </Frame>
  </Step>

  <Step title="Create a Rootly webhook channel" icon="webhook">
    Select **Webhook** as the channel type and configure it with the following values:

    * **Webhook URL**: `https://webhooks.rootly.com/webhooks/incoming/new_relic_webhooks`
    * **Auth type**: Bearer token
    * **Token**: the bearer token shown in your Rootly New Relic integration settings

    <Frame>
      <img alt="New Relic webhook channel configuration" src="https://mintcdn.com/rootly/EZBU89ISF00990Wy/images/integrations/new-relic/alerts/images-2.webp?fit=max&auto=format&n=EZBU89ISF00990Wy&q=85&s=96edd5e6932f656c32931e67fe10c48b" width="857" height="189" data-path="images/integrations/new-relic/alerts/images-2.webp" />
    </Frame>

    <Frame>
      <img alt="New Relic webhook bearer token field" src="https://mintcdn.com/rootly/EZBU89ISF00990Wy/images/integrations/new-relic/alerts/images-3.webp?fit=max&auto=format&n=EZBU89ISF00990Wy&q=85&s=9a15bf00a71d8c34bf99af4a93347176" width="864" height="314" data-path="images/integrations/new-relic/alerts/images-3.webp" />
    </Frame>

    <Callout icon="key" color="#DBEAFE">
      Your bearer token is available in Rootly under **Integrations > New Relic > Configure**.
    </Callout>

    <Frame>
      <img alt="Bearer token in Rootly integration settings" src="https://mintcdn.com/rootly/EZBU89ISF00990Wy/images/integrations/new-relic/alerts/images-4.webp?fit=max&auto=format&n=EZBU89ISF00990Wy&q=85&s=52e63cb7ed90d82c850a50fad3fac317" width="873" height="818" data-path="images/integrations/new-relic/alerts/images-4.webp" />
    </Frame>
  </Step>

  <Step title="Test the webhook" icon="circle-check">
    Click **Test Notification** in New Relic. A test alert should appear on your [Rootly Alerts page](https://rootly.com/account/alerts).

    <Frame>
      <img alt="Test alert appearing in Rootly" src="https://mintcdn.com/rootly/EZBU89ISF00990Wy/images/integrations/new-relic/alerts/images-5.webp?fit=max&auto=format&n=EZBU89ISF00990Wy&q=85&s=81f251e00b99c4a42a2699043699e74b" width="865" height="336" data-path="images/integrations/new-relic/alerts/images-5.webp" />
    </Frame>

    <Callout icon="circle-check" color="#DCFCE7">
      If the test alert appears in Rootly, the integration is working correctly. You can now attach this channel to New Relic alert policies.
    </Callout>
  </Step>
</Steps>

## How Alerts Are Mapped

Rootly extracts the following fields from each New Relic alert payload:

* **Summary** — the `title` field from the New Relic issue
* **External ID** — the issue `id`, used to deduplicate alerts
* **External URL** — the `issueUrl`, linking back to the New Relic issue
* **Labels** — `state`, `trigger`, `priority`, and `workflowName` are attached as Rootly alert labels

<Callout icon="tag" color="#DBEAFE">
  New Relic `priority` and `state` values are available as alert labels in Rootly. You can use these in workflow run conditions to handle critical vs warning alerts differently.
</Callout>

## Troubleshooting

<AccordionGroup>
  <Accordion title="No alerts are appearing in Rootly after a New Relic alert fires" icon="circle-exclamation">
    Verify that the webhook URL and bearer token are correct. Use the **Test Notification** button in New Relic to confirm delivery. Ensure the notification channel is attached to the alert policy that fired.
  </Accordion>

  <Accordion title="Alerts appear but are missing fields" icon="file-circle-question">
    Rootly extracts fields from the standard New Relic issue payload. If your New Relic account uses a customized payload template for the webhook channel, ensure it still includes the standard fields: `title`, `id`, `issueUrl`, `state`, `priority`, and `createdAt`.
  </Accordion>

  <Accordion title="The bearer token is not being accepted" icon="key">
    Confirm you are using the token from the Rootly New Relic integration settings, not your New Relic API key. These are different credentials — the bearer token is generated by Rootly for authenticating inbound webhooks.
  </Accordion>
</AccordionGroup>