TICKET MANAGEMENT
Daily digest of Intercom-detected bugs filed to Linear
On a daily schedule, summarizes which Intercom conversations were promoted to Linear bugs versus deflected as how-to questions, and posts a triage digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionPull last 24h of triaged conversationsIntercom
- ActionQuery Linear issues created this windowLinear
- ActionCompose triage digestOpenAI
- OutputPost digest to SlackSlack
What it does
Runs once a day, gathers every Intercom conversation processed in the last 24 hours, and reports how triage went: how many became Linear bugs, how many were how-to questions, and which bugs are highest severity. It gives the support and engineering leads a single Slack snapshot of the bug intake funnel.
When to use it
When leadership wants a recurring pulse on bug intake quality — what's reaching engineering and what's being deflected — without digging through Intercom or Linear themselves.
How it works
- 1A daily schedule fires the flow (trigger).
- 2Conversations from the trailing 24 hours are pulled from Intercom along with their triage tags.
- 3Linear is queried for issues created from those conversations in the same window.
- 4An LLM composes a digest: bug count, how-to count, top severities, and any conversations stuck as `unclear`.
- 5The digest is posted to a Slack channel with deep links to the new Linear issues.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect OpenAIModels, embeddings, files.
- 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.