TICKET MANAGEMENT
Link new Sentry issues to an existing Linear umbrella bug
When Sentry opens a new issue, this checks whether it matches an existing umbrella bug already tracked in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Sentry issue createdSentry
- ActionLook up fingerprint in umbrella mapping tablePostgres
- LogicBranch: matches an existing umbrella?
- ActionComment Sentry link on Linear umbrella + bump user countLinear
- ActionElse create new Linear bug and store mappingPostgres
What it does
Catches every new issue Sentry surfaces and decides whether it is a fresh bug or just another face of one you already track. Matches go to the existing Linear umbrella issue; only genuinely new crashes create a new ticket.
When to use it
Use it when one root cause throws several Sentry fingerprints and your Linear backlog fills with near-identical bug tickets. It keeps a single umbrella issue authoritative and its affected-user total honest.
How it works
- 1Sentry fires when a new issue is created.
- 2The flow pulls the issue's culprit, fingerprint, and stack signature, then queries Postgres for a known umbrella mapping.
- 3A branch checks for a match: matched issues skip ticket creation; unmatched ones fall through.
- 4On a match, it comments the new Sentry link on the Linear umbrella issue and increments its affected-user custom field.
- 5On no match, it opens a new Linear bug and records the new fingerprint-to-issue mapping in Postgres for next time.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.