Linear

Read and write Linear issues, projects, teams, and cycles from any myai canvas, function, or chat.

Project & Work ManagementAvailable now

Linear is the opinionated issue tracker most modern engineering teams default to instead of Jira — keyboard-first, opinionated workflow, GraphQL API. The integration treats Linear as a live data source for chats, canvases, and functions: issues, projects, teams, cycles, all readable from chat, writable from automations, queryable when the cross-team view doesn't fit a Linear-native filter.

What you can do

  • Pull issue state into a chat — "show me all P1 issues in the platform team that haven't moved in a week" returns a structured table inline.
  • Issue CRUD from automations — create issues, comment, transition status, assign — when conditions fire from CRM, customer support, or anywhere else.
  • Project rollups — for the cross-team project view that Linear's per-team model doesn't quite give you.
  • Cycle awareness — sprint progress, capacity, completion rate, all queryable for status reporting.
  • Label-scoped queries — every "customer-reported" issue, every "tech-debt" issue, queryable as a structured set.
  • Cycle-over-cycle comparison for the "are we getting faster" trend that Linear analytics doesn't quite cover.

How to connect

Linear Personal API Key. Generate one at Settings → API → Personal API keys in your workspace. Sent as Authorization: {api_key} (no Bearer prefix — Linear is opinionated about this).

The integration honors the user's Linear permissions — grant only what the workflows need.

Connect Linear in myai

Common use cases

  • Sprint kickoff digest — function pulls each team's cycle, summarizes by priority and assignee, posts to engineering leads each Monday.
  • Customer-to-Linear automation — high-priority support signal creates a Linear issue in the right team's project with full context inline.
  • Cross-tool engineering queries — combine Linear issue context with GitHub code references for the full "what changed and why" picture.

Reference

  • Connection model: Linear Personal API Key (Bearer-less header — Authorization: {key})
  • API: Linear GraphQL (the integration handles GraphQL composition; functions see a REST-shaped interface)
  • Scope: ~45 operations across issues, projects, teams, cycles, labels
PreviousJiraNextMailchimp