TICKET MANAGEMENT
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…
How it runs
The automated pipeline, trigger to output.
- TriggerNew bug report in Discord channelDiscord
- ActionSummarize and extract search keywords with LLMOpenAI
- ActionSearch Linear for matching open issuesLinear
- LogicDecide if a true duplicate exists
- ActionComment on duplicate or create new Linear issueLinear
- OutputReply in Discord thread with canonical issue linkDiscord
What it does
Prevents duplicate Linear issues from a busy Discord channel. When a new bug arrives, an LLM distills it into search terms, the flow queries open Linear issues, and the model judges whether any existing issue is the same bug. If so, it adds a comment with the new reporter's details and reuses that issue. If not, it creates a new, properly structured issue. The Discord thread is updated either way.
When to use it
Use it when popular bugs get reported many times and your Linear board fills with near-identical issues. This keeps reporter signal attached to a single canonical issue and saves triagers from manual merging.
How it works
- 1A new Discord bug message triggers the flow.
- 2An OpenAI call extracts a normalized summary and candidate search keywords.
- 3The flow searches Linear for open issues matching those keywords.
- 4A logic step asks the model whether a returned issue is a true duplicate.
- 5If duplicate, it comments the new context on the existing Linear issue; otherwise it creates a new structured issue.
- 6It replies in the Discord thread with the canonical issue link.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.