# Create PagerDuty Incident

Learn how to automatically create [PagerDuty](https://www.pagerduty.com/) 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 PagerDuty's incident response platform.

***

#### What You'll Get

When a run fails, Bolt automatically creates a PagerDuty incident containing:

* Incident title with schedule name and workspace
* Incident details including:
  * Direct link to Paradime run logs
  * Run ID and execution details
  * Start and end timestamps
  * Commands executed
  * Branch information
* Urgency level based on your configuration

***

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

* **Leverage existing on-call rotations** - Route data pipeline failures to the right team automatically
* **Unified incident response** - Manage data incidents alongside infrastructure incidents
* **Mobile alerting** - Get notified of critical pipeline failures via SMS, phone, or mobile push
* **Escalation policies** - Ensure critical data issues never go unaddressed
  {% endhint %}

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

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* PagerDuty account with API access
* Valid PagerDuty user email address
* PagerDuty API Key
  {% endhint %}

***

#### Setup Guide

Set up PagerDuty incident creation for failed runs. Follow the steps below, and watch our interactive tutorial.

**Step 1: Gather Your PagerDuty Information**

1. **Generate API Key**:
   * Follow the instructions in Pager Duty Documentation <https://support.pagerduty.com/main/docs/api-access-keys>
   * Create a new API key
   * Copy and save your API key securely
2. **Identify From Email**:
   * Use the email address of a valid PagerDuty user in your account
   * This email must be associated with the account making API requests
   * Typically, this should be a service account or bot user email

**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 select "Create PagerDuty Incident"
3. Fill in the following fields:
   * **Select Schedules**: Choose the schedules for which you want to trigger this webhook. Leave blank or select all for all schedules without filtering
   * **API Key**: Enter the API key you generated in PagerDuty
   * **From Email**: Enter the email address of a valid user associated with the account making the request
   * **Urgency**: Select the urgency level:
     * `high` - For critical pipeline failures requiring immediate attention
     * `low` - For non-critical failures that can be addressed during business hours
4. Click "Connect"

**Step 3: Test the Integration**

1. Run a Bolt schedule manually that will fail (the webhook only triggers on failed runs)
2. After the run fails:
   * Check your PagerDuty dashboard for the new incident
   * Verify the appropriate on-call person was notified
   * Confirm the incident contains all run failure details

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

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2Fh8V5r92xjHJHr4c8Mmfi%2Fimage.png?alt=media&#x26;token=56543e57-3183-4a3c-ad9c-4d872ef5b2c7" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/templates/incident-templates/create-pagerduty-incident.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.