Skip to main content
LINEAR INTEGRATION

​
Issue tracking at the speed your team actually ships.

Any signal — a Sentry alert, a Slack message, a customer email, a form submission — becomes a properly-formed Linear issue in under 60 seconds, with team, priority, assignee, and description pre-filled. Sprint admin disappears. Backlog hygiene runs on a schedule. Your team keeps shipping; Actionist keeps the board clean.

Watch it happen

​
An issue — from chat to closed.

The full lifecycle: an issue created from a Slack message, its status updated mid-sprint, and a final comment linking back to the fix. Pick an event to step through it.

chat · maya · 10:41
youThere’s a checkout bug from Sentry — create a Linear issue for the eng team, high priority.
tool · linear_create_issue
mayaCreated ENG-412 — Checkout fails on coupon apply · team: Engineering · priority: high · assigned: on-call.
mayaSentry event ID and stack trace added to description. Link: linear.app/eng/ENG-412
linear_create_issue — title, team, description (Markdown), assignee, priority (integer), and state all set in one call. The Sentry context lands in the issue body and renders natively in Linear’s editor.
workflow · sprint-sync · 14:05
schedPR #881 merged to main. Branch: fix/ENG-412-coupon-checkout.
tool · linear_get_issue · ENG-412
tool · linear_update_issue · state: In Review
agentENG-412 moved from In Progress to In Review. Priority unchanged: high.
linear_update_issue accepts the human-readable identifier (ENG-412) — no UUID lookup needed when the reference comes from a PR branch name or commit message.
workflow · issue-close · 16:22
schedDeploy succeeded — v2.14.1 live. Affected issue: ENG-412.
tool · linear_add_comment · ENG-412
tool · linear_update_issue · state: Done
agentCommented: “Fixed in v2.14.1 — deploy verified. Sentry event resolved.” Issue closed.
linear_add_comment keeps the full audit trail in Linear itself — Sentry ID, deploy tag, and verification note — without any manual copy-paste. The issue history is self-documenting.
Capabilities

​
What agents can do with Linear.

Seven scopes across the full issue lifecycle — from reading your workspace to writing issues, updates, and comments.

☰
List every team and project in your Linear workspace. Fetch project IDs at workflow setup time and cache them as variables so agents don’t re-fetch on every run.
linear_list_teams
☷
Pull issues filtered by team, state, assignee, or project. Narrow by team first to reduce query cost, then layer on additional filters.
linear_list_issues
☌
Fetch a specific issue by its human-readable identifier (e.g. ENG-123) or internal UUID. Prefer the identifier in workflows where issue references come from Slack messages, PR branch names, or commit messages.
linear_get_issue
+
Create issues with title, team, description (Markdown), assignee, priority, and state — all from a single agent step. Pass Markdown in description and it renders natively in Linear’s editor.
linear_create_issue
✎
Change title, description, assignee, priority, or state on any existing issue. Useful for backlog hygiene sweeps and sprint-boundary automations.
linear_update_issue
☺
Post a top-level comment or thread a reply using parentId. Keeps issue history clean and links back to source context — Sentry IDs, Slack thread URLs, deal notes.
linear_add_comment
Setup

​
Connect Linear.

MCP OAuth is the recommended path — no token management, full action set, and you can limit which Linear teams are exposed during the OAuth step. API key is available as a fallback.

1

Open Apps and find Linear

Click Apps in the sidebar. Find Linear in the apps library and click Connect Linear.
2

Choose a connection method

3

Confirm the connection

Once status shows Connected, Linear tools are available to every agent and workflow in your workspace.
actionist · Apps · LinearNot connected
L
Issue tracking · 6 scopes granted
Connect Linear
Connection method
No token management — recommended
Recommended
Paste a Personal Access Token
linear.app — Authorize Actionist
Actionist is requesting access to your Linear workspace
read:issueswrite:issuesread:teams
Authorize
Workflows

​
Common workflows to start with.

Engineering

A Sentry alert fires, an agent creates a Linear issue with the error context in the description, assigns it to the on-call engineer, and comments with the Sentry link — before anyone checks their inbox.

Engineering

When a Linear sprint (Cycle) ends, an agent collects all closed issues, groups them by owner, and posts the retro summary to Slack before anyone opens Linear.

Sales and support

A closed-deal message lands in Slack. The agent reads the feature gap, creates a Linear issue in the right team with ARR context attached, and links it back to the deal record — no tab-switching, no copy-paste.

Sales and support

A Support agent creates a customer need issue from an escalation ticket, assigns it to the product team, and comments with the original customer message.

Operations

A scheduled agent runs weekly: updates stale priorities, sweeps blocked issues, and adds audit comments — what used to take 30 minutes of clicking completes in under a minute.

Operations

When a campaign brief is approved in Notion, an agent auto-creates a launch checklist issue in Linear and assigns it to the relevant project.

In practice

​
Three recipes teams run every day.

Real workflows, concrete outputs — each one live in under 10 minutes.

Sam · Solo founder
Every morning at 08:55, an agent runs linear_list_issues filtered to In Progress and In Review across all teams, groups them by assignee, and posts a standup digest to Slack before the 09:00 call. Yesterday’s 14 open issues, owners listed, blockers flagged — no one opens Linear just to read the board.
saves ~20 min/day
Priya · Support lead
When a support thread hits a bug-confirmed label in the helpdesk, the agent reads the conversation, calls linear_create_issue with a structured description — repro steps, affected version, customer count — and comments back on the ticket with the Linear link. 23 issues filed last week, zero copy-paste.
saves ~3 hrs/wk
Dario · Sales
At cycle close, the agent calls linear_list_issues filtered to Done in the current cycle, groups by project, and drafts release notes as a Markdown doc — customer-facing language, no jargon. Dario pastes it into the deal room for prospects asking “what shipped this sprint?” — answered before the question lands.
live in 10 min
Limits

​
Limits and gotchas.

25items returned per list call (teams, projects, issues)
0priority = none; 1 = urgent; 2 = high; 3 = normal; 4 = low
1writer per bucket recommended — avoid multi-agent contention on the same issue
ENG-123prefer human-readable identifier over UUID in cross-system references
All list tools (teams, projects, issues) paginate at 25 items per call. Filter by team, state, assignee, or project to narrow the result set before fetching. Filter by teamId first — it reduces query cost and keeps responses faster.
When creating or updating issues, priority is an integer: 0 = none, 1 = urgent, 2 = high, 3 = normal, 4 = low. Spell these out in workflow instructions so agents always set the right value. Priority 1 (urgent) suits on-call assignment workflows; 4 (low) suits backlog items that surface only in sprint planning.
1 — urgent2 — high3 — normal4 — low
Issue fetch and update actions accept either the human-readable identifier (e.g. ENG-123) or the internal UUID. Prefer the identifier in workflows where issue references come from Slack messages, PR branch names, or commit messages — those almost always carry the short form. Use identifier (returned by all issue queries) when posting links to external systems; it is the stable public handle.
If an agent creates or updates issues and you have a trigger on issue changes, the agent’s writes will re-fire the trigger. Stamp a custom label on every agent-touched issue and exclude that label from your trigger filter conditions.
Use the MCP OAuth path over the API key path — no token to rotate, full action set, and you can limit which teams are exposed at OAuth time. To restrict access to specific teams, do it during the OAuth step; you cannot reduce team scope later without disconnecting and reconnecting.
Automate the board

​
Your team ships. Actionist keeps Linear clean.

Connect Linear in two minutes. Let agents handle issue creation, status updates, and backlog hygiene — triggered by every signal your team already produces.

Open the DashboardEmail the team

MCP OAuth — no token to rotate, full action set, team-scoped at connect time.
Issues created in under 60 seconds · Runs on any signal · Backlog hygiene on a schedule.

Keep going

​
Related topics.

https://cdn.simpleicons.org/slack

Slack

Linear and Slack together cover most team automation loops — bug alerts, retro summaries, and approval flows.

MCP

How the Linear MCP server fits into the broader integration model and how to manage OAuth scopes.

Reactions

Wire Linear webhook triggers — new issues, comments, and cycle events — to agents with filter rules and routing.

Schedules

Set up recurring agent runs for backlog hygiene sweeps, sprint retros, and cycle-boundary automations.

Credentials

Store and rotate Linear API keys in the encrypted Credentials Vault without re-editing agents.

Apps

Browse every app Actionist connects to — and see what else fits in your workflow alongside Linear.