TICKET MANAGEMENT
Auto-raise Linear priority when a deduplicated bug crosses a report threshold
Each new Intercom report of a known bug increments its Linear issue count, and when the count crosses configured thresholds the issue's priority is bumped and the eng lead is…
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionFingerprint and match/create Linear issueLinear
- LogicCompare reporter count to thresholds
- ActionUpdate Linear issue priorityLinear
- OutputAlert eng lead in Slack on Urgent crossingSlack
What it does
Makes bug priority self-adjusting. A defect that one person reports stays low; the same defect reported by twenty people automatically climbs to Urgent and pulls in the engineering lead. The decision is driven by the live reporter count, not by who shouts loudest.
When to use it
Use it when you already dedup bugs into Linear and want impact to drive prioritization instead of manual gut calls. Ideal for teams that want a defensible, count-based escalation policy.
How it works
- 1An Intercom conversation tagged `bug` fires the trigger.
- 2OpenAI normalizes the report to a fingerprint and the flow finds (or creates) the matching Linear issue, incrementing its reporter count.
- 3A logic step compares the new count against thresholds: 5 reports moves the issue to High, 15 moves it to Urgent.
- 4If a threshold was just crossed, the flow updates the Linear issue priority.
- 5On an Urgent crossing it posts a Slack alert to the engineering channel naming the issue, count, and last reporter so the lead can react immediately.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 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.