# Linear

Connecting Linear to Zero gives your team clear visibility into issue tracking right inside the CRM. It links customer data with project work, so every bug, feature request, or task is tied to the right account or contact.

With this integration, you can:

* View linked Linear issues directly from customer records.
* Track issue status in real time alongside deal and account progress.

***

## 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="/files/p6SSkzWwRObmUxL3BW2o" alt="" 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="/files/PrtAtoZxWlkeoZAoTFBI" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In Zero, go to **Workspace Settings → Integrations**. Scroll to **Issue Tracker Integrations** and create a new connection.

<figure><img src="/files/SOwRbXxPY11wdZTJC8xL" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

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

<figure><img src="/files/0AjogMjAPOxlcP7IVcp6" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

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

<figure><img src="/files/O4gKqBPl1k7Kk6h08AAb" alt="" 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="/files/BAlKElh3mrkot6HsAQXw" alt="" 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="/files/BE9GSzuCLf5gc0q15CH1" alt="" width="563"><figcaption></figcaption></figure>

* By default, Zero pulls the **last 30 days** of data. You can trigger a **full sync** from the integration settings.

***

## Where the data appears in Zero

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

<figure><img src="/files/9UGw7Cr5CvnPfxdRlDFL" alt="" width="330"><figcaption></figcaption></figure>

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

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

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

<figure><img src="/files/P30BSRZDwDpy3noY6sey" alt=""><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="/files/wvl9RIPyWd9d6loFcW7Q" alt=""><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="/files/Tanh6haZR8N6Y0dqSk03" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.zero.inc/features/integrations/linear.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.