> 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/integrations/incident.io.md).

# incident.io

Connect incident.io to Paradime to receive real-time alerts for your Bolt Pipelines.

{% hint style="info" %}

#### Prerequisites

Before connecting incident.io to Paradime, make sure you have:

* An existing Bolt schedule
* incident.io account with API access
* incident.io API Key
* Configured severity levels in incident.io
  {% endhint %}

### Setup Guide

Set up incident.io incident creation for failed runs by following the steps below.

#### Step 1: Gather Your incident.io Information

**1. Generate API Key**

* Navigate to <https://app.incident.io/settings/api-keys>
* Click **Create API Key**
* Give it a descriptive name (e.g., "Paradime Integration")
* Copy and save your API key securely

{% hint style="warning" %}
**Important:** Store your API key securely. You will need it to configure the Paradime integration.
{% endhint %}

#### Step 2: Connect incident.io to Paradime

1. In Paradime, navigate to **Settings → Integrations → incident.io.**
2. Paste your incident.io API Key into the field provided.
3. Click **Create** to establish the connection.

Once connected, Paradime will automatically create incidents in incident.io whenever Bolt runs fail.

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

### Enable incident.io for Your Bolt Schedules

After enabling the integration, you can configure which Bolt Schedules should create incidents in incident.io when they fail.

To configure incident creation:

1. Navigate to **Bolt** > **Schedules** in the Paradime interface.
2. Select the schedule you want to monitor.
3. Open the [**Integration Settings**](/app-help/documentation/bolt/creating-schedules/trigger-integrations/trigger-incident.io-incidents.md) for that schedule.
4. Enable **incident.io Incident Creation** to automatically create incidents in incident.io when the schedule fails.

Once enabled, any failures in the configured Bolt Schedules will automatically trigger incident creation in incident.io, allowing your team to respond quickly to data pipeline issues.

### incident.io Integration Capabilities

Paradime uses the incident.io API to to automatically create incidents for for [Bolt Schedules](/app-help/documentation/bolt.md).

This integration enables you to:

* Automatically create incidents when dbt™ runs fail
* Leverage Slack-native incident management workflows
* Track MTTR and incident frequency for data pipelines
* Integrate pipeline failures with your on-call rotation
* Maintain centralized incident tracking across your organization
* Use incident.io's timeline and postmortem features for pipeline issues


---

# 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/integrations/incident.io.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.