TICKET MANAGEMENT
Linear Duplicate-Cluster Merge Proposer with Confidence Gate
When a new Linear issue is created, find its closest sibling tickets by embedding similarity, and if confidence is high enough, propose linking them all to one canonical issue.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Linear issue createdLinear
- ActionEmbed issue + query pgvector for nearest siblingsPostgres
- LogicGate on cluster confidence threshold
- ActionPick canonical issue + draft merge rationaleOpenAI
- OutputPost merge proposal with Approve/Reject to SlackSlack
- ActionOn approval, link siblings as duplicates in LinearLinear
What it does
Every new Linear issue is compared against recent open issues to detect duplicate clusters. When a cluster crosses a confidence threshold, the workflow nominates a canonical issue (the oldest or highest-priority sibling) and drafts a merge proposal that links the rest to it. A human approves in Slack before any links are written.
When to use it
For support or triage teams drowning in repeat reports of the same bug. Use it when you want automatic clustering but refuse to auto-merge blindly — the confidence gate plus human approval keeps false merges out.
How it works
- 1A new Linear issue fires the trigger.
- 2OpenAI embeds the title and body, and a Postgres pgvector query returns the nearest open siblings with cosine scores.
- 3A logic gate checks whether the top cluster exceeds the configured confidence threshold; below it, the run exits silently.
- 4OpenAI picks the canonical issue and writes a plain-English rationale for the merge.
- 5A Slack message presents the proposed canonical issue, its siblings, and Approve/Reject buttons.
- 6On approval, Linear marks each sibling as a duplicate of the canonical issue and posts a closing comment.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
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…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.