TICKET MANAGEMENT
Daily digest of Intercom-sourced bugs promoted to Linear
Each morning this summarizes the previous day's bug conversations that were promoted to Linear, groups them by area and severity.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionQuery yesterday's promoted bugsPostgres
- ActionFetch current Linear statusLinear
- LogicGroup by area, severity, impact
- ActionWrite digest narrativeOpenAI
- OutputPost digest to SlackSlack
What it does
Produces a once-a-day readout of which support bugs became Linear issues, so nobody has to scroll two tools. It pulls yesterday's promoted-bug records from Postgres, joins them to current Linear status, groups by product area and severity, and posts a clean digest to a Slack channel with counts, top customer-impact items, and direct links.
When to use it
When support and engineering need a shared daily picture of incoming bug load and triage progress without sitting in a standup or pinging each other in threads.
How it works
- 1A scheduled trigger fires each weekday morning.
- 2The flow queries Postgres for bug conversations promoted to Linear in the last 24 hours.
- 3It fetches current status and assignee for each linked Linear issue.
- 4A logic step groups items by product area and severity and ranks by customer impact.
- 5An OpenAI step writes a concise narrative summary of the trends.
- 6The flow posts the formatted digest with links to a Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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.