Linear integration: connect Linear to Polylane
Connect Linear teams, projects and issues to Polylane with a personal API key. Turn investigation findings into confirmed issue updates with evidence.
Get started for freeWhat Polylane does with Linear.
Findings become issues
When an investigation ends at something your team has to fix, the agent files it in Linear with the evidence trail in the description, on the right team with the right priority.
Issues move with the work
Agents update state, priority, and assignee as the situation changes, and leave comments with what they found, so Linear reflects reality without anyone retyping it.
Queried mid-conversation
Ask what is open, in progress, or assigned to someone and the agent reads it straight from Linear, teams, projects, and issues alike.
How to set up Linear
- Open Linear Settings → Security & access → Personal API keys and create a write-capable key.
- Paste the personal key into Polylane and validate it against the workspace; this flow does not accept an OAuth token.
- For webhook-driven triage, connect with a workspace admin’s key. A non-admin key still connects, but webhook provisioning is skipped.
Permissions and access
The key needs write access for issue creation and updates. Polylane sends the personal key directly in the Authorization header, without a Bearer prefix. Issue writes ask for confirmation; arbitrary GraphQL mutations pass the same confirmation gate.
Discovery, refresh and the connected view
Agents list teams, workflow states, members and projects, then search or read issues with recent comments. Updates can change state, priority, assignee, project, labels and due date. The admin-created webhook covers issues in public teams: urgent issues become alerts, and de-escalating or completing an issue resolves the alert.
Example workflow
Turn a completed investigation into a Linear issue with the evidence trail in its description. After confirmation, assign it to the responsible team member and comment with the findings. If that issue becomes urgent in a public team, the webhook can bring it back into triage without someone pasting the ticket into a new thread.
Disconnect and revoke access
Disconnect Linear in Polylane, then revoke its personal API key under Linear Security & access. A missing webhook does not mean the issue tools are unavailable; check whether the connected user was a workspace admin.
Tools for the investigation.
What Polylane can do with Linear while it investigates. Every call is recorded in the transcript.
linearApi Run any Linear GraphQL query or mutation that lacks a dedicated tool
linearTeams List Linear teams, workflow states, and members
linearProjects List Linear projects and their delivery state
linearIssues Read, search, create, update, and comment on Linear issues
Common questions.
Do I need to be a Linear admin to connect?
No. A non-admin personal key can connect and use the agent tools. Workspace admin rights are required only to create the triage webhook.
Will Polylane update Linear issues without confirmation?
Issue writes ask for confirmation before executing, including mutations through the generic GraphQL tool.