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

# Linear

"When is that fix shipping?" is a question sales shouldn't have to ask in Slack. Connecting Linear ties bugs, feature requests and tasks to the account or contact that raised them, so the status is on the record next to the deal.

## How to connect Linear to Zero

{% stepper %}
{% step %}
In Linear, open your workspace **Settings → Security & access**.

Or use this link format (replace the placeholder with your workspace slug):\
`https://linear.app/{your-workspace}/settings/account/security`\
\&#xNAN;*Example:* `https://linear.app/zero-crm/settings/account/security`
{% endstep %}

{% step %}
Generate a new **personal API key**.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_security_access_settings.png" alt="Linear Security &#x26; access settings page with the Personal API keys section and New API key button" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Grant at least **Read access** for the key. The key is copied to your clipboard and can’t be viewed again, so store it somewhere safe.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_api_key_created.png" alt="Linear access key details showing the API key, copy-it-now notice and Permissions" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In Zero, go to **Settings → Connections → Integrations**. Scroll to **Issue Tracker integrations** and select **Connect Issue Tracker**.
{% endstep %}

{% step %}
Select **Linear**, paste the API key you just created into **Issue Tracker API Key**, and click **Connect Integration**.
{% endstep %}

{% step %}
After connecting, you’ll see this confirmation view.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_integration_connected_status.png" alt="Issue Tracker integrations list showing a Linear Issue Integration with Connected status" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## How the integration works

* Zero maps Linear issues to companies by linking them to associated **customer requests**.
* To link an issue to a company in Zero, make sure the Linear issue is connected to a **customer request**.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_new_issue_customer_request.png" alt="Linear New issue dialog with the Add customer request dropdown selecting a customer" width="563"><figcaption></figcaption></figure>

* Zero maps customer requests to company records by **domain**. Add the domain to your **Customer** objects in **Linear** (go to **Customers**, edit the customer, and add the domain). The domain must match the company’s domain in Zero.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_edit_customer_domains_modal.png" alt="Linear Edit customer modal with a domain entered in the Domains field" width="563"><figcaption></figcaption></figure>

* The integration updates hourly. You can pull data on demand with **Sync data** in the integration's `⋯` menu.

## Where the data appears in Zero

* In any list, add the properties related to **Issues**. These fields are shared with the other issue trackers: Plain, Pylon, Front, and Intercom.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_issues_property_picker.png" alt="Add a property menu listing Issues, Issues by month, Open issues, # of issues and # of open issues" width="330"><figcaption></figcaption></figure>

* **Issues** and **Open issues** give you a quick preview of total and open items, respectively.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_issues_columns_company_grid.png" alt="Companies grid row with # of issues, Issues and Issues by month columns populated"><figcaption></figcaption></figure>

* Click an issue to see a quick preview and open it directly in Linear.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_issue_preview_open_in_linear.png" alt="Issue preview panel showing the issue title, creator and an Open in Linear link"><figcaption></figcaption></figure>

* **Issues by month** shows how many issues a customer has raised over time. Hover over the bubbles to see a month-by-month breakdown.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_issues_by_month_sparkline.png" alt="Issues by month sparkline with a hover tooltip showing the count for one month"><figcaption></figcaption></figure>

* You can also use **Issues** as an entity in [**Reports**](/features/reports.md) to chart the data and pin it to dashboards.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/linear_issues_per_month_report.png" alt="Report builder with a stacked bar chart of issues per month by company and Issues as the entity"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zero.inc/settings/integrations/linear.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.