TICKET MANAGEMENT
Nightly Sweep of Open Intercom Bugs with Repro Attempts into Linear
On a nightly schedule, an agent pulls open bug-tagged Intercom conversations without a Linear link, attempts to reproduce each.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionList unlinked bug-tagged Intercom conversationsIntercom
- ActionReproduce each report in sandbox browserBrowserbase
- LogicBranch: confirmed / not reproduced / needs info
- ActionCreate labeled Linear issue per conversationLinear
- OutputPost sweep summary to SlackSlack
What it does
Sweeps the bug backlog so nothing slips through. Each night it finds bug-tagged Intercom conversations that were never escalated, attempts to reproduce each one, and files the result in Linear, closing the gap left by busy support shifts.
When to use it
Use it as a safety net behind real-time triage, or when adopting reproduction tooling on an existing backlog. Best for teams that suspect tagged bugs are being missed during high-volume periods.
How it works
- 1A nightly schedule triggers the sweep.
- 2The agent lists open Intercom conversations tagged `bug` that have no linked Linear issue.
- 3It iterates each conversation, extracting steps and reproducing in a sandbox browser.
- 4A branch routes confirmed, not-reproduced, and insufficient-info outcomes differently.
- 5For each, it creates a Linear issue with the outcome label and repro notes.
- 6It posts a summary of the night's sweep, counts, and any blockers to Slack for the morning standup.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 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.