Skip to main content
New Introducing Mosaic Learn more
Productivity integration

Linear + Conversion

Let Conversion agents pick up Linear issues, work through attached files, and comment back.

Linear
Two-way
Conversion

How Conversion works with Linear

Conversion connects to Linear so a Conversion agent, an AI teammate with its own instructions and permissions, can pick up issues and work through them. A Linear trigger wakes the agent when a matching issue is created, updated, or commented on, and the agent reads the issue, its comments, and any attached files. It reports back by commenting on or changing the status of that one issue, so an agent scoped to a label can't touch tickets outside it.

What you can do

Scoped by filters

Filter a trigger by team, project, label, status, priority, or assignee. A dedicated label like conversion-agent picks up exactly the issues someone tagged.

Attached files, processed

Attach a partner list or CSV to an issue and the agent reads and transforms it in its sandbox, then produces a new file for you to download.

A conversation on the ticket

A Comment added trigger also handles follow-ups, so you can review the agent's work and tell it to go ahead on the same issue.

Locked to one issue

Comments and status changes apply only to the issue that started the session, and the agent's own comments never wake it up again.

What syncs

Data Direction Details
Issues and comments Into Conversion The triggering issue and its comments reach the agent, and later comments continue the same session.
Attachments Into Conversion Files on the issue or its comments, such as spreadsheets and CSVs, which the agent can read and transform.
Comments Out of Conversion Posted on the triggering issue only, by the agent's own Linear app user.
Status changes Out of Conversion The agent can move the triggering issue to another workflow state, and no other issue.

How to connect Linear

  1. 1 In Conversion, open Workspace settings > AI, choose Linear under Integrations, and authorize as a Linear workspace admin. Each Conversion workspace connects to one Linear workspace.
  2. 2 In Linear, open Settings > Applications > Conversion Agent and choose which teams the agent can see. Private teams are excluded until you add them.
  3. 3 On a custom agent's Configuration tab, add a Linear trigger, pick an event such as Comment added, and add filters.
  4. 4 Set each tool to Automatic, Requires approval, or Disabled on the agent's Tools tab, then tag a test issue.
FAQ

Linear integration FAQ

Yes. Conversion connects to Linear so a Conversion agent, an AI teammate with its own instructions and permissions, can pick up issues and work through them. A Linear trigger wakes the agent when a matching issue is created, updated, or commented on, and the agent reads the issue, its comments, and any attached files. It reports back by commenting on or changing the status of that one issue, so an agent scoped to a label can't touch tickets outside it.

Only the teams granted in Linear under Settings > Applications > Conversion Agent. Access starts at all public teams, so issues in a private team reach no agent until a Linear admin adds that team.

No. Comments and status changes are locked to the issue that started the session, even if someone asks for more, so an agent scoped to one label never touches issues outside it.

Comment added, in most cases. It fires only when a person deliberately comments, and it handles their follow-up messages in the same session. Issue updated fires on every edit and interrupts work in progress, so use it only when you need that.

Yes. Each agent with a matching trigger gets its own session on the issue, with its own comments. If one agent should own a kind of ticket, scope agents with different labels.

See Conversion with Linear

Book a demo and we'll walk through the Linear integration on a stack that looks like yours.