> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/linear.md).

# Linear

Connect Linear to Heeler over OAuth for two-way issue creation, updates, and closure.

Heeler runs a **two-way** integration with Linear — creating, updating, and closing issues, and harvesting Projects, Members, and Teams to automate issue context. It connects over **OAuth**.

## What Heeler needs

You'll grant Heeler access to:

* View basic information about projects, members, and teams in your workspace.
* View profile details about people in your workspace.
* Send messages as `@heeler`.
* Upload, edit, and delete issues as the Heeler Security App.

## Connect Linear

{% stepper %}
{% step %}

### Add the integration

Go to **Administration → Integrations → Add Integration → Linear**.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-f1e58577ed1ae55bbd3bc536e8165db252dda37d%2Fcc-int-linear-01.png?alt=media" alt="The Add Integration menu in Heeler with Linear selected."><figcaption><p>Add Integration → Linear.</p></figcaption></figure>
{% endstep %}

{% step %}

### Authorize

If you have more than one workspace, pick the right one, then scope Heeler's access — **All public teams** is recommended — and click **Authorize**.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-e859fad00a8efa86b014f3138477936806387daa%2Fcc-int-linear-02.png?alt=media" alt="Linear&#x27;s authorization screen scoping Heeler&#x27;s access to the workspace, with the Authorize button."><figcaption><p>Scope access to All public teams and click <strong>Authorize</strong>.</p></figcaption></figure>
{% endstep %}

{% step %}

### Verify

A confirmation appears and the integration shows **Healthy**. Linear is now a destination in [Workflows](/mrecEO40m5D6bt7Pq5pE/operate/workflows.md) and [team routing](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/team-ticket-settings.md).

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-d8bdfdad1661e3c3307d03fa558955af8df68457%2Fcc-int-linear-03.png?alt=media" alt="The Heeler Integrations list showing the Linear integration with a Healthy status."><figcaption><p>The connected Linear integration, Healthy.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Refreshing credentials

Heeler uses short-lived credentials refreshed automatically. If the connection breaks, open the **⋯** menu on the Linear row and choose **Refresh Token** — failure to refresh is the most common cause of a broken connection.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-0249ba2b06a96ce9458495483b063b585f69abf5%2Fcc-int-linear-04.png?alt=media" alt="The row action menu on the Linear integration with the Refresh Token option."><figcaption><p>Choose <strong>Refresh Token</strong> to re-run the credential refresh and restore the connection.</p></figcaption></figure>

## Related

* [Team Ticket Settings](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/team-ticket-settings.md) — route each team's findings to its Linear team.


---

# 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.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/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.