---
title: "Connect New Relic"
description: "Send New Relic alert issues to Firefight through a workflow and a Webhook destination."
canonical: https://firefight.app/docs/alerts/new-relic
---

# Connect New Relic

Firefight has a dedicated alert source for New Relic alerts. A New Relic workflow notifies a Webhook destination with its default payload, and the alert resolves in Firefight when New Relic closes the issue.

## Set up the Firefight side

Go to **Settings → Alert Sources**, click **Add source**, give it a name like "New Relic production", and pick the **New Relic** provider. When you create it, Firefight opens the source's setup. It shows the ingest URL and a **Copy token** button for the source's secret token, and the same steps as this page.

## Set up the New Relic side

1. In New Relic, open **Alerts → Destinations** and add a **Webhook** destination. Paste the ingest URL as the **Endpoint URL**.
2. Turn on **Use authorization**, choose **Bearer Token**, paste the token, and save the destination.
3. In **Alerts → Workflows**, add or edit a workflow and notify the Webhook destination. Keep the default payload template.
4. Notify when issues are activated and when they are closed.

Requests that fail the check are rejected with `401`, and the source's row in **Settings → Alert Sources** shows the rejection.

## What Firefight reads

Each alert gets these fields, which you can match in your [routing rules](https://firefight.app/docs/alerts/routing-rules.md).

| Field | Value |
|---|---|
| `title` | The issue's title |
| `description` | The alert policy and condition names |
| `service` | The first impacted entity |
| `severity_raw` | The issue's priority, such as `CRITICAL` |
| `url` | The issue in New Relic |

The alert's title in Slack and on the dashboard links to its page in New Relic.

## Firing and resolving

An issue fires an alert the first time New Relic notifies about it. Later notifications for the same issue count on that alert, and the notification for a closed issue resolves it.

See [Grouping & deduplication](https://firefight.app/docs/alerts/grouping-and-deduplication.md) for how repeat firings collapse into one alert.