TICKET MANAGEMENT
Merge Linear issues sharing a Sentry fingerprint
When a new Sentry issue links to a Linear ticket, finds other open Linear issues tied to the same Sentry fingerprint, merges them into the oldest as duplicates.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue alert with linked Linear ticketSentry
- ActionFind open Linear issues with same fingerprintLinear
- LogicTwo or more matches found?
- ActionMark newer issues duplicate of oldestLinear
- ActionConsolidate subscribers onto canonicalLinear
- OutputPost merge summary to Slack triageSlack
What it does
When Sentry escalates an error to Linear, this workflow checks whether any other open Linear issues already point at the same Sentry fingerprint (the stack-trace identity Sentry uses to group events). If it finds matches, it picks the oldest issue as the canonical one, marks the others as duplicates, links them, and consolidates every subscriber so nobody loses the thread.
When to use it
Use it when the same crash is reported by multiple users or services and lands as several near-identical Linear tickets. It keeps your triage board clean and ensures one source of truth per root cause instead of a scatter of half-tracked duplicates.
How it works
- 1A Sentry issue alert fires and includes the linked Linear issue and its fingerprint.
- 2The flow queries Linear for other open issues carrying the same Sentry fingerprint.
- 3A branch checks whether two or more matches exist; if only one, it exits quietly.
- 4It selects the oldest issue as canonical and marks the rest as duplicate, linking each to the canonical.
- 5It copies all subscribers from the duplicates onto the canonical issue.
- 6It posts a summary of the merge to the team's Slack triage channel.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
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.