> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Linear

> Connect Overcut to your Linear workspace to create, update, and comment on issues directly from your automations.

# Linear Integration

Overcut connects to Linear so your agents can open, update, and comment on issues without leaving the workflow. After you authorize the connection, Linear teams appear alongside your existing ticket providers, letting you automate planning and status updates across every tool your organisation uses.

## Overview

With Linear connected you can:

* **Create issues** from detections, check-ins, or any trigger in your workflow
* **Update titles, descriptions, labels, and assignees** as work progresses
* **Synchronise labels** between Overcut and Linear to ensure workflows can filter and route tickets accurately
* **Reference Linear issues** in end-to-end workflow recipes that combine code, data, and planning tasks

## Connecting Linear

<Steps>
  <Step title="Open Integrations">
    In Overcut, navigate to **Settings → Integrations** and click **Connect Linear**.
  </Step>

  <Step title="Authorize Overcut in Linear">
    Overcut redirects you to Linear’s authorization screen. Review the requested scopes and click **Authorize**. Overcut needs permission to read and write issues, comments, and labels so agents can operate on your behalf.
  </Step>

  <Step title="Map Linear Teams (optional)">
    After authorization, choose which **Linear teams** should appear as **Ticket Repositories** in Overcut. Each selected team becomes a repository you can reference in triggers and actions.
  </Step>

  <Step title="Finish Setup">
    Click **Save & Finish**. Connected teams are now visible under **Repositories → Tickets** and available in workflow builders.
  </Step>
</Steps>

## Provider-Specific Behaviors

* **Team as Repository**: Each Linear team you select is treated as a separate ticket repository. You can target specific teams in triggers and actions just like you would with GitHub or Jira projects.
* **Status names**: Issue trigger filters (such as **Status From** and **Status To**) use the exact workflow status names configured for the selected team (for example, Triage, Backlog, In Progress, Done). Names differ by team. Linear provides the destination status but not the previous status, so **Status To** filters work reliably while **Status From** will not match.
* **Linked issue relationships**: Agents can create, remove, and read linked issue relationships in Linear. Linear uses its own relationship names (agents can inspect the available types before linking). See the [tools reference](/docs/reference/tools) for how linked relationships work across providers.

## Automations and Agent Workflows

Once connected, Linear issues become a first-class citizen inside the Overcut workflow builder. Agents can **create**, **update**, and **comment** on issues the same way they already interact with GitHub or Jira.

<CardGroup cols={2}>
  <Card title="Create an Issue" icon="circle-plus">
    Generate a new Linear issue from any trigger such as a failing test, Sentry alert, or Slack slash command.
  </Card>

  <Card title="Update an Issue" icon="pen-to-square">
    Edit titles, descriptions, labels, or assignees as your workflow progresses and new context emerges.
  </Card>

  <Card title="Close & Resolve" icon="check-double">
    Mark issues as <em>Done</em> or <em>Canceled</em> when a pipeline finishes successfully or when a rollback is triggered.
  </Card>
</CardGroup>

## Next Steps

* Learn about [workflow quick starts](/docs/quick-starts) for more automation recipes.