> 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/documentation/bolt/creating-schedules/templates/ticketing-templates/create-linear-issues.md).

# Create Linear Issues

Learn how to automatically monitor your data pipeline and create Linear issues 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 Linear's issue tracking system.

### What You'll Get

When a run fails, Bolt automatically creates a Linear issue containing:

* Schedule name and workspace
* Various Run details to help you debug, like:
  * Run ID with link to Paradime
  * Start and end time
  * Commands executed
  * Branch information

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

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

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

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

* Existing [Bolt schedule](https://app.paradime.io/bolt)
* Admin access to Linear
* [Linear API Key](https://developers.linear.app/docs/graphql/working-with-the-graphql-api#personal-api-keys)
  {% endhint %}

***

### Setup Guide

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

#### Step 1: Gather you Linear Credentials

1. Copy your Linear team name. Find information on [Linear Teams](https://linear.app/docs/teams).
2. Create a new API key:
   1. Go to Linear's [Security & access settings](https://developers.linear.app/docs/graphql/working-with-the-graphql-api#personal-api-keys)
   2. Create a new API key in Personal API Keys section
   3. Save the API key securely

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

#### Step 2: Configure the Webhook

1. In [Bolt](https://app.paradime.io/bolt), navigate to the lefthand panel and click [**Templates**](https://app.paradime.io/bolt/templates)
2. Click **Ticketing** and use the "Create Linear Issue" template
3. Enter your:
   * Linear Team Name (example: `DATA`)
   * API Key
4. Click "Connect"

#### Step 3: Test the Integration

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

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


---

# 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/documentation/bolt/creating-schedules/templates/ticketing-templates/create-linear-issues.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.