Per-pair page

Claude + Linear: AI-first triage and writing inside the issue tracker.

Use Claude to triage Linear issues, summarize project status, draft technical specs, or auto-link related work. Built for engineering teams that already think AI-first.

Connect Anthropic and Linear See reverse direction

Trigger app

Anthropic as the trigger

Workflows fire when something happens in Anthropic.

Anthropic has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Linear as the action

Workflows do something in Linear, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Anthropic → Linear

When something happens in Anthropic, do it in Linear.

0 Anthropic triggers wired to 8 Linear actions.

Linear → Anthropic

Or fire it the other way around.

6 Linear triggers wired to 21 Anthropic actions downstream.

See Linear → Anthropic →

Popular pairings

Common Anthropic → Linear workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 0 of 0 combinations

How it works

Connect Anthropic and Linear in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Anthropic and Linear
Open Tiny Command, authorize Anthropic and Linear once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Anthropic trigger
Drop the Anthropic → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/anthropic.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Linear action
Drop the Linear → Add Comment action below it. Map fields from the Anthropic payload into the Linear inputs.
linear.create-comment
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Anthropic + Linear.

How does Claude triage new Linear issues?

Linear Issue Created → Claude reads title + description → returns team, project, priority, estimate, and labels. Workflow applies via Update Issue and adds a "triaged-by-ai" label so humans know what touched it.

Can Claude write technical specs from a Linear issue?

Yes. Prompt: "Expand this issue into a technical spec with problem statement, proposed approach, alternatives considered, and rollout plan". Save as a Linear document attached to the issue, ready for engineer review.

How do I detect Linear issues that depend on other issues?

On Issue Created, search the project for similar issues, pass them to Claude with "identify dependencies — issues that block or are blocked by this new one". Apply relationships via Linear's Issue Relations API.

Can Claude generate a weekly Linear status update?

Yes. Scheduled Friday afternoon: list closed and in-progress issues for the team this week, pass to Claude with "write a weekly engineering update for stakeholders, group by project, highlight risks". Email to the team and slack ##all-eng.

How do I prevent Claude from changing fields a human already set?

Skip triage if the issue already has the "triaged-by-ai" or "triaged-by-human" label. Or only run on issues created from external sources (Intercom, Slack, support widget) where no human has touched them yet.

What's the right Claude model for Linear automation?

Haiku for triage and label suggestions (fast, cheap). Sonnet for spec writing and status updates (the default). Opus only for long-context analyses across many issues — usually overkill for per-issue workflows.

Other apps that pair well with Anthropic.

Anthropic + Gmail

Anthropic + Slack

Communication

Anthropic + Google Sheets

Spreadsheets & Databases

Wire Anthropic to Linear in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo