Linear

Agile development issue tracking.

What it does

Creates and updates Linear issues. The same job as Jira, for teams on Linear.

What you need

An account with Linear that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Linear's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.

Connecting it

Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.

Open the project and stay on the Visual Editor tab.
Open the Tools & Integrations rail on the right.
Find Linear and press Connect.
Authorise in the window that opens, then come back. The rail will show it as connected.

The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.

To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Linear's own security settings, which works even if you never open RAiN again.

What an agent can do with it

15 actions are available once connected, 3 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected Linear is never offered them.

Action	What it does
`linear_create_linear_project`	Create Project
`linear_create_project_milestone`	Create Project Milestone
`linear_create_project_update`	Create Project Update
`linear_create_team`	Create Team
`linear_get_current_user`	Get current user
`linear_list_comments`	List comments
`linear_list_project_updates`	List project updates
`linear_remove_issue_label`	Remove label from Linear issue ⚠️ deletes things
`linear_remove_reaction`	Remove reaction from comment ⚠️ deletes things
`linear_run_query_or_mutation`	Run Query or Mutation ⚠️ deletes things
`linear_search_issues`	Search Linear issues
`linear_update_linear_project`	Update Project
`linear_update_project_update`	Update Project Update
`linear_update_team`	Update Team
…	and 1 more, all listed in the rail

Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.

A worked example

An agent watching error reports opens one Linear issue per distinct failure and links the occurrences, instead of a channel full of duplicates.

When it goes wrong

Team id is required and is not the team name. Take it from a list action once and keep it.