TICKET MANAGEMENT
Reproduce Intercom Bug Reports and Attach Repro Steps to Linear
When a support conversation in Intercom is tagged as a bug, an agent reads the thread, attempts to reproduce the issue in a sandbox browser.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionFetch full transcript and attachmentsIntercom
- ActionExtract claimed steps and expected resultOpenAI
- ActionReplay steps in a sandbox browserBrowserbase
- LogicBranch: reproduced vs. not reproduced
- OutputCreate Linear issue with repro steps and labelLinear
What it does
Turns a tagged Intercom bug report into a Linear issue that engineering can act on immediately. Instead of a vague "app is broken" ticket, engineers get an issue that already states whether the bug reproduces, the exact steps, and the environment.
When to use it
Use it when support and engineering work in different tools and bugs lose detail in the handoff. Best for teams who tag bug conversations in Intercom but want a reproduction attempt before an engineer is paged.
How it works
- 1An Intercom conversation receives the `bug` tag, firing the trigger.
- 2The agent pulls the full conversation transcript, customer metadata, and any attachments.
- 3An LLM extracts the claimed steps, expected result, and affected URL or feature.
- 4The agent drives a headless browser to walk through the steps and capture the outcome.
- 5A branch decides reproduced vs. not-reproduced based on the observed result.
- 6A Linear issue is created with a clear title, the repro steps, environment, and a reproduced/needs-more-info label.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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.