> For the complete documentation index, see [llms.txt](https://docs.kognitos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kognitos.com/guides/platform/integrations/linear.md).
# Linear
{% hint style="info" %}
The following documentation is for **Linear v1.4.0**.
{% endhint %}
## Overview
Linear is a modern issue tracking and project management tool designed for software development teams. This integration allows automated issue creation, status updates, project tracking, and team workflow management. Enhance development productivity and maintain organized project tracking.
## Setup
The following integrations need to be connected to your Kognitos workspace:
* **Linear**
### Steps
Follow these steps to connect the integration in Kognitos:
{% stepper %}
{% step %}
#### Navigate
Using the left navigation menu, go to **Integrations** → **Explore Integrations**.
{% endstep %}
{% step %}
#### Find
Search for the integration and click on it.
{% endstep %}
{% step %}
#### Connect
Click on **Connect** to add a connection to the integration.
{% endstep %}
{% step %}
#### Configure
Add a name for the connection. You'll be prompted for [**authentication**](#authentication) details if needed. Then, click on **Connect**.
{% endstep %}
{% endstepper %}
## Authentication
Use one of the following authentication methods to connect this integration in Kognitos. Each method has its own configuration requirements.
### Connect using Personal API Key
Connect to Linear using a Personal API Key.
| Label | Description | Type |
| ---------------- | ------------------------------------------------------ | ----------- |
| Personal API Key | Your Linear Personal API Key (starts with lin\_api\_). | `sensitive` |
### Sign in with Linear
To connect to the **Linear** book, click on Sign in with Linear. This will redirect you to Linear's secure authentication page where you can sign in with your Linear account and authorize the application.
## Actions
The following actions are available in the **Linear** integration:
### 1. Add a label to a linear issue
Apply a label to a Linear issue.
### 2. Add an issue to a linear cycle
Add a Linear issue to a cycle (sprint).
### 3. Create a comment on a linear issue
Post a comment on a Linear issue.
### 4. Create a linear project
Create a new project in Linear.
### 5. Create an issue
Create an issue in Linear.
### 6. Delete a linear comment
Delete a comment from a Linear issue.
### 7. Delete an issue from linear
Delete a Linear issue.
### 8. Follow a linear issue
Subscribe the authenticated user to a Linear issue to receive notifications.
### 9. Get a linear issue by id
Fetch a single Linear issue by UUID, identifier, or issue number.
### 10. Get a linear user
Find a Linear workspace user by their display name or email address.
### 11. Get all linear users
List all users in the Linear workspace.
### 12. Get the comments from a linear issue
Fetch all comments on a Linear issue.
### 13. Get the cycles of a linear team
List all cycles (sprints) for a Linear team.
### 14. Get the issues
Fetch the issues matching the filters (if any).
### 15. Get the labels
Fetch all available issue label names in the workspace.
### 16. Get the notifications from linear
Fetch notifications for the authenticated Linear user.
### 17. Get the projects from linear
Fetch projects in the Linear workspace matching the filters (if any).
### 18. Get the teams
Fetch the teams matching the filters (if any).
### 19. Get the users from a team
Get the users from a team.
### 20. Get the workflow states of a linear team
List all workflow states available in a Linear team.
### 21. Remove a label from a linear issue
Remove a label from a Linear issue.
### 22. Search linear issues
Full-text search Linear issues.
### 23. Update a linear comment
Edit the text of an existing Linear comment.
### 24. Update a linear project
Edit a Linear project's name or description.
### 25. Update an issue in linear
Update fields on an existing Linear issue.
## Concepts
### Linear issue
An issue in Linear
| Field Name | Description | Type |
| -------------------------- | ----------------------------------------------------------------------- | ------------------------ |
| `id` | The unique identifier for the issue. | `text` |
| `number` | The number of the issue. | `number` |
| `team` | The team the issue belongs to. | `json` |
| `description` | The description of the issue. | `text` |
| `title` | The title of the issue. | `text` |
| `state` | The state of the issue. | `json` |
| `identifier` | The workspace identifier for the issue, such as "INT-123". | `optional[text]` |
| `priority` | The numeric Linear priority. | `optional[number]` |
| `priority_label` | The human-readable priority label. | `optional[text]` |
| `url` | The Linear web URL for the issue. | `optional[text]` |
| `team_name` | The name of the team the issue belongs to (e.g. "Integrations"). | `optional[text]` |
| `team_key` | The short key of the team the issue belongs to (e.g. "INT"). | `optional[text]` |
| [`assignee`](#linear-user) | The user assigned to the issue, if any. | `optional[linear user]` |
| `labels` | The label names applied to the issue. | `optional[list of text]` |
| `label_names` | The label names joined into one string, for filtering (e.g. "Bug, P1"). | `optional[text]` |
| `project_id` | The ID of the project this issue belongs to, if any. | `optional[text]` |
| `project_name` | The name of the project this issue belongs to, if any. | `optional[text]` |
| `cycle_id` | The ID of the cycle this issue is in, if any. | `optional[text]` |
| `cycle_number` | The number of the cycle this issue is in, if any. | `optional[number]` |
| `created_at` | The ISO timestamp when the issue was created. | `optional[text]` |
| `updated_at` | The ISO timestamp when the issue was last updated. | `optional[text]` |
### Linear team
A team in Linear
| Field Name | Description | Type |
| ---------- | ----------------------------------- | ------ |
| `id` | The unique identifier for the team. | `text` |
| `name` | The name of the team. | `text` |
| `key` | The short identifier for the team. | `text` |
### Linear user
A user in Linear
| Field Name | Description | Type |
| ---------- | -------------------------------------------- | --------- |
| `id` | The unique identifier for the user. | `text` |
| `email` | The email address of the user. | `text` |
| `name` | The name of the user. | `text` |
| `is_me` | Whether this user is the authenticated user. | `boolean` |
### Linear cycle
A cycle (sprint) in Linear
| Field Name | Description | Type |
| ------------- | --------------------------------------------------- | ---------------- |
| `id` | The unique identifier for the cycle. | `text` |
| `number` | The sequential number of the cycle within its team. | `number` |
| `name` | The display name of the cycle, if set. | `optional[text]` |
| `description` | An optional description of the cycle. | `optional[text]` |
| `starts_at` | The ISO timestamp when the cycle starts. | `optional[text]` |
| `ends_at` | The ISO timestamp when the cycle ends. | `optional[text]` |
### Linear comment
A comment on a Linear issue
| Field Name | Description | Type |
| ------------ | ---------------------------------------------------- | ---------------- |
| `id` | The unique identifier for the comment. | `text` |
| `body` | The text body of the comment. | `text` |
| `url` | The Linear web URL for the comment. | `optional[text]` |
| `created_at` | The ISO timestamp when the comment was created. | `optional[text]` |
| `updated_at` | The ISO timestamp when the comment was last updated. | `optional[text]` |
### Linear project
A project in Linear
| Field Name | Description | Type |
| ------------- | ----------------------------------------------------------------------------- | ---------------- |
| `id` | The unique identifier for the project. | `text` |
| `name` | The display name of the project. | `text` |
| `state` | The current state of the project name (e.g. Backlog, In Progress, Completed). | `optional[text]` |
| `description` | An optional description of the project. | `optional[text]` |
| `url` | The Linear web URL for the project. | `optional[text]` |
| `start_date` | The project start date (YYYY-MM-DD), if set. | `optional[text]` |
| `target_date` | The project target date (YYYY-MM-DD), if set. | `optional[text]` |
### Linear notification
A notification for the authenticated Linear user
| Field Name | Description | Type |
| ------------ | --------------------------------------------------------- | ---------------- |
| `id` | The unique identifier for the notification. | `text` |
| `type` | The notification type (e.g. issueAssignee, issueComment). | `text` |
| `read_at` | ISO timestamp when the notification was read, if read. | `optional[text]` |
| `url` | The Linear web URL related to the notification. | `optional[text]` |
| `created_at` | The ISO timestamp when the notification was created. | `optional[text]` |
| `updated_at` | The ISO timestamp when the notification was last updated. | `optional[text]` |
### Linear workflow state
A workflow state in Linear
| Field Name | Description | Type |
| ------------- | ------------------------------------------------------------------ | ---------------- |
| `id` | The unique identifier for the state. | `text` |
| `name` | The display name of the state. | `text` |
| `state_type` | The Linear type of the state (e.g. started, completed, cancelled). | `text` |
| `description` | An optional description of the state. | `optional[text]` |
---
# 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.kognitos.com/guides/platform/integrations/linear.md?ask=&goal=
```
`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.