TICKET MANAGEMENT
Link new Sentry crash groups to existing Linear issues (or open a new one)
When Sentry opens a new crash group, search Linear for a matching bug and attach the event to it; if none exists, create a new Linear issue seeded with stack trace and breadcrumbs.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry new issue (crash group) webhookSentry
- LogicNormalize error fingerprint (exception + top frame)
- ActionSearch Linear for matching open issueLinear
- LogicBranch: existing match vs. no match
- ActionComment on match OR create seeded Linear issueLinear
- OutputWrite Linear URL back to Sentry as external linkSentry
What it does
Stops duplicate bug tickets from piling up. Every time Sentry surfaces a new error group, this checks whether you already track that bug in Linear. If a match exists it attaches the fresh occurrence; if not, it files one clean issue with the crash context already filled in.
When to use it
Use it when on-call engineers keep re-filing the same crash, or when your Sentry-to-tracker handoff is manual and noisy. Ideal for teams that want one Linear issue per root cause, not one per alert.
How it works
- 1Sentry fires a webhook on a newly created issue (crash group).
- 2The flow normalizes the error fingerprint (exception type + top frame).
- 3It searches Linear for an open issue carrying that fingerprint label or matching title.
- 4Branch: if a match is found, it comments on the existing Linear issue with the new event count, environment, and Sentry permalink.
- 5If no match, it creates a Linear issue seeded with the stack trace, breadcrumbs, release, and fingerprint label.
- 6It writes the Linear issue URL back to the Sentry group as an external link so the two stay bonded.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.