Linear is Actionist’s preferred issue tracker integration. Use it to capture work from chat, generate triaged backlogs, or notify on status changes.Documentation Index
Fetch the complete documentation index at: https://learn.actionist.ai/llms.txt
Use this file to discover all available pages before exploring further.
What you can do
- Create issues with title, description, assignee, team, project, labels, priority, estimate, cycle.
- Query issues by team, status, label, assignee, or saved view.
- Update status and properties on existing issues.
- Add comments and react to comments.
- Subscribe to webhooks for issue created / updated / commented.
Setup
Install the Linear MCP server
Integrations → Discover → Linear → Install. Authenticate with a Linear API key generated under Settings → API in Linear.
Scope the key
Use a key tied to a specific service user, not your personal account — easier to audit later. Limit team scopes to the ones Actionist should touch.
Common workflows
- Chat → issue. “Open a Linear ticket in
ENGtitled ‘Fix the search latency p99’, assign Priya, P2.” Actionist drafts the issue, you approve, it lands. - Daily triage digest — every morning, list all newly-created P0/P1 issues in
#engineeringwith owner suggestions. - Standup auto-generator — Friday at 4 pm, summarize each engineer’s closed issues for the week into a per-person Notion page.
- PR ↔ ticket linker — when a GitHub PR opens with
[ENG-123]in the title, comment on the Linear ticket with the PR link.
Limits & gotchas
- API key vs OAuth. Personal API keys see everything that user can see. Use a service account or OAuth scope for production.
- Cycles auto-roll. “Current cycle” workflows must compute the cycle ID at run time, not pin it.
- Webhooks require a public endpoint. Use Actionist’s webhook trigger URL or expose a tunnel.