> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/integrations/linear.md).

# Linear

Connect Pump to Linear to turn cloud cost anomalies and infrastructure reccomendations into actionable engineering work. Create and manage Linear issues directly from Pump, assign issues to teammates, and track remediation progress without leaving your cloud dashboard.

**Setup time:** \~1–2 minutes

***

### Overview

Pump's Linear integration bridges cloud optimization with engineering execution. Instead of manually copying anomalies into your issue tracker, you can create and manage Linear issues directly from Pump.

Whether you're responding to a cloud cost anomaly or assigning a infrastructure recommendations, Pump keeps your engineering workflow and cloud operations synchronized.

> **Note:** Linear is a work tracking integration. Pump does **not** read Linear usage or billing data.

***

### Prerequisites

Before connecting Linear, you'll need:

* Access to the Linear workspace you want to connect
* Permission to authorize applications in your Linear workspace
* Browser pop-ups enabled for Pump (required for OAuth authentication)

***

### Setup Instructions

1. In Pump, navigate to **Settings → Integrations**.
2. Find **Linear** and click **Connect with Linear**.
3. Authorize Pump on the Linear OAuth consent screen.
4. Open any cloud cost anomaly
5. Click **Create Linear Issue**.
6. Select:
   * Team
   * Assignee
   * Issue title
   * Issue description
   * Workflow status
7. Click **Create**.

Pump immediately creates the issue in Linear and links it back to the original Pump finding. As your engineering team updates the issue, Pump automatically synchronizes the latest status.

***

### Permissions Pump Requests

| Permission | Why Pump Needs It                                                                                             |
| ---------- | ------------------------------------------------------------------------------------------------------------- |
| **Read**   | Retrieve your Linear teams, workflow statuses, and teammates so issues can be created and assigned correctly. |
| **Write**  | Create Linear issues directly from Pump.                                                                      |

***

### Features

#### Create Linear Issues from Pump

Create a Linear issue directly from:

* Cloud cost anomalies

When creating an issue, you can:

* Select the appropriate Linear team
* Assign the issue to any teammate
* Customize the issue title
* Edit the issue description before submission
* Select the initial workflow status

This allows engineering teams to begin remediation immediately without manually recreating context.

***

#### Assign Findings to Team Members

Assign every anomaly to the appropriate engineer during issue creation.

Assignments remain visible inside Pump, making ownership clear across engineering, operations, and finance teams.

***

#### Live Issue Status Sync

Pump continuously synchronizes with Linear so you can monitor progress without switching tools.

As issues move through your team's workflow, Pump automatically updates the linked finding with the latest Linear status, including both default and custom workflow states.

***

### What Pump Uses Linear For

Pump uses Linear to:

* Create issues from cloud cost anomalies and infrastructure reccomendations
* Prefill issue titles and descriptions with relevant context
* Link every issue back to the originating Pump finding
* Synchronize issue status and assignee automatically

Pump **does not** automatically create issues for every anomaly—you remain in control of which findings become engineering work.

***

### Security & Access

Pump stores OAuth credentials securely using encryption at rest.

The integration only accesses the metadata required to:

* Create Linear issues
* Retrieve teams and workflow statuses
* Keep linked issue status synchronized

To disconnect Linear:

1. Open **Settings → Integrations → Linear** in Pump.
2. Click **Disconnect**.

To completely revoke access, also remove the Pump application from your Linear workspace settings.

***

### Supported Workflows

The Linear integration supports:

* Creating issues for cloud cost anomalies
* Assigning issues to teammates
* Editing issue titles before creation
* Editing issue descriptions before creation
* Selecting the initial workflow status
* Live synchronization of issue status back into Pump

***

### FAQ

#### I don't see any teams when creating an issue.

Confirm you've connected the correct Linear workspace and that your account has access to at least one team.

#### Can I create multiple Linear issues for the same anomaly?

No. Each Pump finding can be linked to a single Linear issue.

#### Does disconnecting Linear revoke access completely?

Disconnecting removes the integration from Pump. To fully revoke access, also remove the Pump app from your Linear workspace settings.


---

# 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://help.pump.co/integrations/linear.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.
