Skip to main content
Connect Linear so RubixKube agents can see your projects and teams, create tickets from insights and RCAs, and keep incident state in sync with the tool your team already tracks work in.

​
What it unlocks

Read teams and projects

Agents know which team or project owns each service, so tickets land in the right place.

Create and update issues

Open issues from insights or RCA reports with evidence and recommended actions prefilled.

Status awareness

Agents can read status and assignee on their own tickets to decide whether to escalate, update, or close.

Tenant-wide by default

Enable once. Every agent across every environment can use Linear.

​
Connect it

1

Open the Integrations page

In the RubixKube console, go to Integrations and select Linear.
2

Authenticate

Authorise with Linear. An admin completes the OAuth flow.
3

Configure access

Pick the teams and projects RubixKube can work with. Optionally set a default team for tickets that have no explicit mapping.
Once connected, Linear is available tenant-wide.

​
How the agents use it

  • Agents can create tickets from insights or RCAs with the full context attached.
  • Chat can answer questions about open incident tickets, ownership, and status.
  • Bridge skills can connect Linear to other tools in your stack, for example surfacing weekly ticket summaries into Notion.

​
Build custom workflows with skills

The connection exposes Linear capabilities to agents. Specific workflows (auto-create tickets above a severity threshold, route to a team based on service ownership, weekly ticket digest, ticket-to-doc sync) are built as Skills.

​
Troubleshooting

Either adjust the default team in the integration settings, or build a skill that maps services to Linear teams based on your ownership model.
Reauthorise from Integrations → Linear. Long-lived OAuth tokens sometimes need a refresh.

Notion

Pair with Linear for ticket-to-doc workflows.

Skills

How to compose Linear capabilities into workflows.