Linear connections
What is it?
Clankee shows one Linear integration in the catalog, but you may connect two separate accounts for different purposes:
| Connection purpose | Used for |
|---|---|
| Agent tools | Agents, chats, and skills |
| Automations | Automation trigger setup |
Each connection is a named account on the same Linear integration. You only need both if you use agents and automations with Linear.
Agent tools connection
When you choose Agent tools, Clankee authorizes as the Linear app — a bot inside Linear that Clankee can assign to issues and mention in comments.
Use this connection when:
- Agents should act on behalf of Clankee in Linear
- You install or enable Linear-related skills
- Clankee needs app-level behavior in issues and comments
Automations connection
When you choose Automations, Clankee authorizes as you (the user completing OAuth). Trigger setup needs admin-level access in Linear so Clankee can register webhooks and listen for workspace events.
That admin scope sounds broad, but automations are mostly read-and-react: they watch for events (for example, an issue was created) and start a workflow. They rarely write to Linear and usually do not access sensitive data — unlike agent tools, which may create issues, post comments, or update work on your behalf.
Use this connection when:
- You create automations that react to Linear events
- Clankee needs to wire Composio triggers against your Linear workspace
Why both connections exist
Linear treats app authorization and user authorization as different OAuth grants. A single token generally cannot serve both:
- An app connection works well for agentic work but may not support automation trigger setup.
- A user/admin connection works well for triggers — admin rights are needed to register them — but does not give agents app-specific behavior (assignable, mentionable bot).
The admin grant for automations is mainly for trigger registration and event listening, not for broad read/write access to your workspace data.
Clankee asks you to pick the purpose at connect time so each feature uses the right account.
How to tell accounts apart
After connecting, open Integrations → Linear. Connected accounts show a badge:
| Badge | Meaning |
|---|---|
| Agentic | For agents, chats, and skills |
| Automations only | For automation triggers |
Use clear Integration name values (for example “Linear — agents” and “Linear — automations”) if you connect both.
How to connect
Open Integrations
Project sidebar → Integrations → Linear.
Choose connection purpose
In Connect Linear, pick Agent tools or Automations. Use the info icon next to Connection purpose for a short summary.
Name and authorize
Enter an Integration name, choose Connect, and complete Linear authorization. Repeat with the other purpose if you need both.
Tips
- Connect Agent tools first if you use Linear skills or agent chat.
- Connect Automations separately when you build Linear-triggered automations.
- The Automations OAuth grant includes admin scope for trigger setup — not because automations need broad write access. Most automation flows only react to events.
- Automations and agent tools each filter to the matching account — you cannot reuse the wrong connection type for the other feature.