TICKET MANAGEMENT
Front Bug Severity Triage and Linear Router
Classifies each incoming bug conversation by severity using OpenAI, then routes it: critical bugs become high-priority Linear issues with a Slack alert.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Front conversation tagged 'bug'Front
- ActionFetch conversation thread and subjectFront
- ActionClassify severity and extract repro stepsOpenAI
- LogicBranch on severity (critical / major / minor)
- ActionCreate Linear issue at mapped priorityLinear
- OutputAlert on-call Slack channel if criticalSlack
What it does
Reads the text of a new bug conversation in Front, scores its severity and reproducibility with an LLM, and creates a Linear issue at the matching priority. Critical-severity reports also page the on-call channel in Slack so they don't sit in a queue.
When to use it
Use it when bug volume is high enough that manual triage is the bottleneck, and you want consistent priority assignment plus instant escalation for outages and data-loss reports.
How it works
- 1A new conversation tagged `bug` in Front triggers the flow.
- 2The conversation thread and subject are fetched from Front.
- 3OpenAI classifies severity (critical/major/minor) and extracts repro steps and affected component.
- 4A logic branch routes on the severity label.
- 5A Linear issue is created with priority mapped from severity and the extracted repro steps in the description.
- 6If severity is critical, a Slack message is posted to the on-call channel with the Linear link and customer impact summary.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.