TICKET MANAGEMENT
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…
How it runs
The automated pipeline, trigger to output.
- TriggerNew bug report in Discord channelDiscord
- ActionClassify severity and summarize with LLMOpenAI
- LogicBranch on severity: critical vs. normal
- ActionCritical: open PagerDuty incident for on-callPagerDuty
- ActionNormal: create prioritized Linear issueLinear
- OutputReply in Discord thread with routing outcomeDiscord
What it does
Reads incoming Discord bug reports and decides how urgent they are. Low and medium bugs become standard Linear issues for the backlog. Anything the model classifies as critical (data loss, outage, security) skips the queue and opens a PagerDuty incident so the on-call engineer is paged right away. Either path posts the outcome back to the Discord thread.
When to use it
Use it when your Discord community surfaces both routine bugs and the occasional production fire, and you can't afford a critical report sitting unread in a channel overnight. The severity gate ensures urgent issues reach on-call while everything else flows into normal tracking.
How it works
- 1A new message in the Discord bug channel triggers the flow.
- 2An OpenAI call classifies the report's severity and writes a short summary.
- 3A logic branch checks the severity level.
- 4Critical reports open a PagerDuty incident with the summary and reporter context.
- 5Non-critical reports create a Linear issue tagged with the inferred priority.
- 6The flow replies in the Discord thread noting where the report was routed.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.
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.