> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/new-relic/new-relic-workflow.md).
# New Relic Workflow Integration
Send New Relic alert events to ilert so on-call engineers get notified of application or infrastructure anomalies promptly with clear escalation.
With [New Relic](https://newrelic.com/)'s integration in ilert, alerts from application or infrastructure monitoring – like error rates, transaction slowdowns, or deployment impacts – are sent to on-call teams via ilert. Automated routes and escalation policies help teams detect issues and respond before they affect service quality.
## In ilert: Create a New Relic alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **New Relic**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In New Relic: Add ilert as a Destination
1. In the sidebar, go to **Alerts & AI** -> **Destinations** -> **Webhook**
2. Enter a **Webhook name** and in the field **Endpoint URL** insert the Webhook URL generated in ilert.
3. On the sidebar go to **Alert conditions (Policies)**
4. Click on the **New alert policy** button.
5. Enter an **Alert policy name** and click on the **Set up notifications** button
6. On the next step click on **Webhook**
7. Enter a channel name and choose the previous created destination in the **Destination** field.
8. To test this channel, we need to change the values of both keys: `state` and `trigger` to "ACTIVATED" and "STATE\_CHANGED". This prevents the testing of an already closed alert. Click on **Send test notification**. After testing, click on **Revert changes** and save the message.
9. On the next page click on **Activate workflow**, to save and activate the workflow.
## FAQ
**Will alerts in ilert be resolved automatically?**
Yes, as soon as an issue has been closed in New Relic, the associated alert in ilert will be resolved automatically.
**Will alerts in ilert be accepted automatically?**
Yes, as soon as an issue has been acknowledged, the associated alert in ilert will be accepted automatically.
**Can I use customised tags for my alerts?**
Yes, customised tags will appear in the alert details tab.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/new-relic/new-relic-workflow.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
