# Linear AI integration on Definable

> Linear is a streamlined issue tracking and project planning tool for modern teams, featuring fast workflows, keyboard shortcuts, and GitHub integrations

## What this connects

Linear is a streamlined issue tracking and project planning tool for modern teams, featuring fast workflows, keyboard shortcuts, and GitHub integrations

Vendor: https://linear.app

## Tools available

**32** tools available. First 12:

- `LINEAR_CREATE_ATTACHMENT` — Create attachment — Creates a new attachment and associates it with a specific, existing Linear issue.
- `LINEAR_CREATE_COMMENT_REACTION` — Add reaction to comment — Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
- `LINEAR_CREATE_LINEAR_COMMENT` — Create a comment — Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.
- `LINEAR_CREATE_LINEAR_ISSUE` — Create linear issue — Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state_id, assignee_id, cycle_id, label_ids, project_id) must belong to the same team as team_id. The created issue's id is returned in data.id — capture it for use as parent_id in sub-issues or follow-up operations. No template_id field exists; expand templates manually into title and description before calling.
- `LINEAR_CREATE_LINEAR_ISSUE_RELATION` — Create issue relation — Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues.
- `LINEAR_CREATE_LINEAR_LABEL` — Create a label — Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and existing labels return the same object structure; check the label's `createdAt` or compare IDs to determine if creation occurred.
- `LINEAR_CREATE_LINEAR_PROJECT` — Create Project — Creates a new Linear project with specified name and team associations.
- `LINEAR_CREATE_PROJECT_MILESTONE` — Create Project Milestone — Tool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to track progress within a project.
- `LINEAR_CREATE_PROJECT_UPDATE` — Create Project Update — Tool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcements for a project.
- `LINEAR_DELETE_LINEAR_ISSUE` — Delete issue — Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Archiving is permanent with no built-in undo — confirm the issue identifier and title with the user before executing, especially in bulk operations.
- `LINEAR_GET_ALL_LINEAR_TEAMS` — Get all teams (Deprecated) — DEPRECATED: Use ListLinearTeams instead (returns paginated payloads with members and projects); this tool returns simpler id/name-level data for all teams visible to the connected workspace with no server-side filtering. Match teams on stable team id, not display name, as names are not guaranteed unique. Partial results reflect workspace permission scope, not tool failure. Skip this call if team_id values are already known.
- `LINEAR_GET_ATTACHMENT` — Download issue attachments — Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension.

## Auth

Auth schemes: `OAUTH2`, `API_KEY`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use Linear

Inside a Definable workflow, Linear is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Linear** — the Researcher (GPT-5.5) pulls context from Linear (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Linear** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Linear (create record, post message, draft email).
- **Designer / Engineer → Distributor → Linear** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Linear (attach file, open PR comment, post status).

The Verifier checks every Linear call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- project management — https://definable.ai/apps/category/project-management/
- task management — https://definable.ai/apps/category/task-management/

## Related

- HTML page: https://definable.ai/apps/linear/
- Same category (project management): https://definable.ai/apps/category/project-management/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt