TICKET MANAGEMENT
Promote Intercom bug conversations to Linear with extracted repro steps
When a support agent tags an Intercom conversation as a bug, this extracts clean reproduction steps, environment, and expected-vs-actual behavior from the thread and files…
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionFetch full conversation transcriptIntercom
- ActionExtract repro steps, env, expected vs actualOpenAI
- LogicRequire valid repro before filing
- ActionCreate structured Linear bug issueLinear
- OutputPost Linear link as Intercom noteIntercom
What it does
Turns a tagged Intercom support thread into a ready-to-triage Linear bug. It reads the full conversation, uses an LLM to pull out reproduction steps, affected environment, and expected-versus-actual behavior, then opens a Linear issue with that structure already filled in. The Intercom conversation gets a note with the issue link so the agent can keep replying to the customer.
When to use it
When support agents triage in Intercom but engineering lives in Linear, and bug reports arrive as messy back-and-forth threads that someone has to hand-rewrite before an engineer will touch them.
How it works
- 1An agent applies the "bug" tag to an Intercom conversation, firing the trigger.
- 2The flow fetches the complete conversation transcript from Intercom.
- 3An OpenAI step extracts structured fields: title, steps to reproduce, environment, expected result, actual result.
- 4A logic step checks the extraction has at least one repro step and a clear actual-vs-expected; if not, it routes back to the agent for clarification instead of filing noise.
- 5A Linear issue is created with the structured body and a source link.
- 6The flow posts the Linear URL back as an internal note on the Intercom conversation.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.