> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/bolt/creating-schedules/templates/incident-templates/create-new-relic-incidents.md).

# Create New Relic Incidents

Learn how to automatically create New Relic incidents when dbt™ runs fail in Bolt. This integration helps data teams track and respond to pipeline failures efficiently by connecting Bolt's pipeline monitoring with New Relic's incident management system.

### What You'll Get

When a run fails, Bolt automatically creates a New Relic incident containing:

* Issue title with schedule name
* Description including:
  * Link to Paradime run logs
  * Run details:
    * Run ID
    * Start and end time
    * Commands executed
    * Branch information

<figure><img src="/files/5soO0iiOzQ1oMCTCPqth" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**Key Benefits for Data Teams**

* Automatic New Relic incident creation when dbt™ pipelines fail
* Real-time pipeline monitoring and incident tracking
* Streamlined workflow between dbt™ runs and New Relic
* Faster response time to pipeline failures
  {% endhint %}

{% hint style="warning" %}
**Prerequisites for New Relic Integration**

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* Admin access to New Relic
* Access to New Relic [Account ID](https://docs.newrelic.com/docs/accounts/accounts-billing/account-structure/account-id/) and [API Key](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/)
  {% endhint %}

***

### Setup Guide

Set up New Relic incident creation for failed runs. Follow the steps below, and watch our [interactive tutorial](#step-3-test-the-integration).

#### Step 1: Gather Your New Relic Credentials

1. **Get Your Account ID**:
   * Visit <https://docs.newrelic.com/docs/accounts/accounts-billing/account-structure/account-id/>
   * Follow instructions to locate your Account ID
2. **Generate API Key**:
   * Visit <https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/>
   * Create a new API key
   * Save this key securely

<figure><img src="/files/uuAiI29jSg5Uigd7YZZ2" alt=""><figcaption></figcaption></figure>

### Step 2: Configure the Webhook

1. From the [Bolt](https://app.paradime.io/bolt) home screen, go to [Templates](https://app.paradime.io/bolt/templates)
2. Click **Ticketing** and use "Create New Relic Incident"
3. Enter your New Relic Credentials:
   * Account ID
   * API Key
4. Click "Connect"

<figure><img src="/files/XnnN0oEqRthLMIk9wRkH" alt=""><figcaption></figcaption></figure>

#### Step 3: Test the Integration

1. [Run a Bolt schedule manually](/app-help/documentation/bolt/managing-schedules/schedule-configurations.md#trigger-a-run-manually) (the webhook only triggers on failed runs)
2. After the run fails, check your New Relic dashboard for the new incident
3. Verify the incident contains run failure details

{% @arcade/embed url="<https://app.arcade.software/share/1wliPq7dW73hEcSBu8YZ>" flowId="1wliPq7dW73hEcSBu8YZ" %}


---

# 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.paradime.io/app-help/products/bolt/creating-schedules/templates/incident-templates/create-new-relic-incidents.md?ask=<question>&goal=<endgoal>
```

`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.