TICKET MANAGEMENT
Intercom bug report to scoped Linear issue with repro steps
When a support teammate tags an Intercom conversation as a bug, an AI agent reads the full thread, extracts clean reproduction steps.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionFetch full thread + customer metadataIntercom
- ActionExtract repro steps, expected/actual, environment
- LogicRepro steps present? else flag for human
- ActionCreate scoped Linear triage issueLinear
- OutputPost Linear link as private Intercom noteIntercom
What it does
Turns a messy Intercom support thread into an engineering-ready Linear bug. When a teammate applies the `bug` tag, an agent reads the entire conversation, distills the customer's complaint into numbered reproduction steps, expected vs. actual behavior, and affected area, then opens a Linear issue with that scope plus a link back to the original conversation.
When to use it
Use when support agents keep pasting half-baked tickets into Linear and engineers bounce them for missing repro steps. It enforces a consistent bug shape without the support team learning Linear conventions.
How it works
- 1An Intercom conversation gets tagged `bug`, firing the trigger.
- 2The agent pulls the full message history and customer metadata from Intercom.
- 3It extracts a title, numbered reproduction steps, expected/actual behavior, and environment hints from the thread.
- 4A logic step checks the repro steps are non-empty; thin reports are flagged for human review instead of filed.
- 5A Linear issue is created in the triage team with the scoped body and a source link.
- 6The agent posts a private note back on the Intercom conversation with the Linear issue URL.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
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.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
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.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.