Integrations · Projects & issues

Linear in the conversation.

A fast issue tracker built for product teams that live in the keyboard. Connect it once and your copilot works with issues, projects, cycles, teams and labels without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

Linear

Projects & issues

01 · COPILOT

Ask for it in plain language. It does the Linear part.

Copilot rides inside the inbox. With Linear connected it reads issues, projects, cycles, teams and labels and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Search issues by team, label, status or text
Read an issue and its comments
Create an issue on the right team with labels
Comment on an issue
Move an issue’s state or assignee

What a specific connection exposes is decided by Linear, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Linear. A workflow starts.

Once Linear is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

An issue is created
An issue changes state

The picker is the authority on which events your Linear connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Linear tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Linear said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Linear tools you left enabled and nothing else.

What teams do with it

Two ways Linear earns its connection.

Support to backlog in one sentence

"File this as a bug on the web team" — Copilot creates the Linear issue with the thread attached and hands back the identifier.

Close the loop automatically

A workflow triggered on issue completion messages every customer whose conversation was linked to it.

Setup

Connect Linear in about a minute.

1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
2
Find Linear in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Linear from its card.
3
Authorize with your own Linear account
You sign in on Linear's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

Linear questions.

How do I connect Linear to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Linear. Connecting it opens Linear's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.

What can Cloodot do in Linear?

Work of this kind: search issues by team, label, status or text; read an issue and its comments; create an issue on the right team with labels; comment on an issue; move an issue’s state or assignee. The exact list depends on what your Linear account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Linear tools Cloodot may use?

Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Linear connection is a matter of leaving the writes off.

Can an event in Linear start a Cloodot workflow?

Yes. Events like an issue is created, an issue changes state appear in the workflow editor's trigger picker once Linear is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Linear?

Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Linear account that authorized it, so a projects & issues connection is only ever as broad as the account behind it.

More projects & issues