TICKET MANAGEMENT
Reproduce Intercom Bugs and Merge Duplicates into Existing Linear Issues
On a tagged Intercom bug, an agent reproduces the issue, searches Linear for an existing matching issue.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionExtract normalized symptom signatureOpenAI
- ActionConfirm bug in sandbox browserBrowserbase
- ActionSearch Linear for matching open issueLinear
- LogicBranch: duplicate or new?
- OutputComment evidence on existing or create new Linear issueLinear
What it does
Stops the same bug from spawning ten Linear issues. The agent reproduces the report, then checks whether an open issue already describes it; if so, it adds the new customer as evidence and bumps priority signal rather than creating a duplicate.
When to use it
Use it when a single high-impact bug generates a flood of separate tickets and engineers lose the true frequency signal. Best for support teams during incidents or buggy releases.
How it works
- 1An Intercom conversation tagged `bug` triggers the flow.
- 2The agent extracts a normalized symptom signature from the thread.
- 3It reproduces the behavior in a sandbox browser to confirm it is real.
- 4It searches Linear for open issues matching the signature.
- 5A branch decides duplicate vs. new.
- 6On a match, the agent comments the new report and customer count onto the existing issue; otherwise it creates a new issue with full repro steps.
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.