Linear

· #215 most-used

Issue tracking at the speed your team actually ships

ProjectsDeveloperProductivityCommunicationAutomation

Linear is the issue tracker built for software teams who move fast — sprints, roadmaps, cycles, and customer feedback all live in one opinionated interface designed to stay out of the way. Connect it to Actionist and your agents can create issues from any signal, triage by label, update statuses at sprint boundaries, surface blockers before standups, and log customer needs against account records — all in plain English, all without opening a new tab.

Try Linear with Actionist Visit Linear

Average time saved

11 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Eliminates the manual work of copying bug reports into issues, updating statuses after deploys, and compiling sprint metrics from the backlog.

Schedule

What your Linear agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs

7Agents at work

24/7Always on

Agents

Tue–Thu

Tue

Wed

Thu

10a

11a

12p

Multi-app workflows

Linear × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows

9Apps spanned

~55 hrsSaved / week

6Personas served

For customer success

Featured4 apps

Bug-to-fix loop, closed in minutes

When a customer emails a bug report, your agent reads the message, finds the matching Linear issue or creates one with full context, attaches the customer email as a link, posts a 'received — investigating' comment, and drops a follow-up reminder on the CS calendar — the entire intake loop that used to take 20 minutes of tab-switching completes before the customer hits refresh.

~23 hrs / week

Time saved for your team — every week, on autopilot

The flow

Trigger·When a bug report email arrives in the shared support inbox

trigger

Step 1

Gmail

Detect incoming bug report email

read

Step 2

Linear

Find existing issue by keyword match

write

Step 3

Linear

Create issue or add customer comment

write

Step 4

Slack

Notify CS team channel with issue link

write

Step 5

Google Calendar

Schedule follow-up reminder for CSM

Result

Create issue or add customer commentNotify CS team channel with issue linkSchedule follow-up reminder for CSM

The win

Saved per run

1.5 hrs

Runs / week

~15×

Every bug report lands in Linear within 60 seconds

Driven byCustomer Support Agent

ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

Sales
19 min / week
Feature-gap logging
Rep manually opens Linear after every demo to file a feature request, often forgetting by end of day.
Sales Agent
0 min
Agent logs gap mid-call
Agent detects the Slack message, creates the Linear issue with ARR context, and links the HubSpot deal — before the call ends.
Marketing
14 min / week
Launch issue creation
Marketing coordinator manually creates 'launch day' issues in Linear each time a campaign activates.
Marketing Agent
0 min
Agent creates on campaign start
Agent detects the activated campaign in HubSpot and creates the Linear monitoring issue with checklist automatically.
Customer Support
19 min / week
Bug intake triage
Support rep reads customer email, opens Linear, creates issue, pastes description, assigns team — 15+ clicks per report.
Customer Support Agent
0 min
Agent creates issue on email
Agent reads the email, finds or creates the Linear issue, posts an acknowledgement comment, and pings the team in Slack.
Human Resources
8 min / week
Onboarding task creation
HR manually creates Linear onboarding issues for each new hire joining the engineering team.
Human Resources Agent
0 min
Agent generates onboarding set
Agent detects the new HRIS entry and creates the full Linear onboarding issue set with assignees pre-filled.
Finance
14 min / week
Budget-to-project linking
Finance manually cross-references Linear projects against budget line items in spreadsheets each month.
Finance Agent
0 min
Agent links on budget entry
Agent reads the new budget line, finds the matching Linear project, and posts the figure as a comment — both systems stay synced.
Operations
30 min / week
Intake-to-issue conversion
Ops coordinator reads the intake spreadsheet daily and manually creates Linear issues for each new request.
Operations Agent
0 min
Agent converts row on creation
Agent detects the new spreadsheet row and creates the Linear issue with team, priority, and description in under 60 seconds.
Legal
6 min / week
Compliance issue filing
Legal manually opens Linear to file compliance or vendor issues flagged in contract reviews.
Legal Agent
0 min
Agent files on document flag
Agent detects flagged contract language and creates the Linear issue with the clause excerpt and risk label attached.

+ 100s of other Linear automations

Average monthly

11 hrs / person / month

Average monthly

11 hrs / person / month

Calculator

Calculate what your team saves

Team size

10 people

Hourly rate

$20 / hr

Hours saved / week

Hours saved / year

1,400

Annual ROI

$28,000

Based on Linear's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.8 hrs / person / week of admin work automated.

Connect

How to plug Linear into Actionist

Pick the connection method that suits your environment.

The fastest path. Install Linear's official MCP server in one click; the agent reaches your workspace through a permissioned OAuth handshake and can read issues, projects, cycles, and labels without any token management.

Open the Apps tab

Find Linear in the Apps library and click Connect. MCP is selected by default.

Authorise in Linear

A Linear OAuth window opens — sign in and grant Actionist read/write access to your workspace. Choose which teams to expose if you want to limit scope.

Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

21 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

10 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Linear

Reusable agent skills that work well alongside this app.

Linear

Query and manage Linear issues, projects, cycles, and team workflows using plain-language commands.

Linear API

GraphQL-native Linear integration with managed OAuth — create, update, and query issues, teams, cycles, and labels programmatically.

Google Forms

Create forms, add question sets, and retrieve responses to feed issue-creation workflows with structured input data.

MCP servers

MCP servers that work with Linear

Connect Actionist to MCP servers built for or around this app.

linear

Official

Official Linear MCP server — full read/write access to issues, projects, teams, cycles, and labels via permissioned OAuth.

Linear

Official

Official Linear MCP wrapping the GraphQL API over OAuth — ideal for teams managing multiple workspaces.

tacticlaunch/mcp-linear

Community MCP server integrating with the Linear project management API for issue and project operations.

FAQs

Questions about Linear + Actionist

How do I connect Linear to Actionist?

Open the Apps tab, find Linear, and click Connect. MCP is the recommended path — Actionist opens a Linear OAuth window where you authorise access to your workspace. Alternatively, generate a personal API key under Linear Settings → Security & access → Personal API keys and paste it in the API key field. The MCP route requires no token management and supports the full action set.

What permissions does the Linear connection need?

The MCP connection uses OAuth and requests read/write access to your issues, projects, cycles, labels, comments, and customer records. If you want to restrict scope, you can limit which teams are exposed during the OAuth authorisation step. The API key method inherits the permissions of the key owner — use a dedicated service account for production automations to avoid accidental over-reach.

Can I use Linear alongside other apps in Actionist workflows?

Yes — Linear is designed as a hub alongside any combination of Slack, Gmail, GitHub, Notion, HubSpot, Google Sheets, and Stripe. Common patterns: GitHub PR opened → Linear issue updated; Slack feature-gap message → Linear issue created; Linear cycle completed → Notion retro page written. Every step.appId in the workflow editor resolves to a logo in the manifest, so all common partners are pre-wired.

How do I avoid trigger loops when my agent updates issues?

Two safeguards prevent loops. First, add an agent-authored-by check: stamp a custom field or label (e.g. 'actionist-updated') on every issue the agent touches, and filter your trigger to exclude issues with that label. Second, use the 'Updated Issue' webhook trigger with a status-change filter so the trigger only fires on human-initiated status transitions, not on the agent's own writes. Both together make recursive loops structurally impossible.

Which Linear objects does Actionist support?

Actionist covers the core objects: Issues (create, read, update, delete, add link, add label, remove label, attach files, add comments), Projects (create, read by ID), Customers (create, find by ID), and Customer Needs (create). Triggers cover the full webhook surface: new/updated issues, comments, labels, projects, customers, cycles, initiatives, and document comments. MCP additionally exposes cycles and team-level reads via GraphQL.

Can the agent react to Linear triggers in real time?

Yes. Linear's webhook-based triggers — New Issue, Updated Issue, New Issue Comment, New Customer, New Project Update, and others — fire within seconds of the event. The agent receives the payload, processes it, and can write back to Linear or fan out to Slack, Gmail, or HubSpot before the next page refresh. Polling-based triggers (General resource) run on the configured schedule interval, typically every minute.

How does the agent handle Linear rate limits?

Linear's API allows 1,500 requests per hour per OAuth app. Actionist batches reads where possible and spaces writes at least 500 ms apart. For high-volume automations — such as bulk issue creation during a sprint kickoff — the agent will queue and retry automatically if a 429 response is received. You can inspect the retry log in the workflow run history to confirm all writes completed.

Can I disconnect Linear without losing my workflow history?

Yes. Disconnecting Linear in the Apps tab revokes the OAuth token or removes the API key from Actionist's credential store — it does not delete your Linear data. Existing workflow run logs retain the issue IDs and action names from past executions. If you reconnect, all previously configured workflows resume immediately with no reconfiguration needed.