TICKET MANAGEMENT
Dedupe Intercom bug reports against open Linear issues
Before filing a new Linear bug from an Intercom thread, this checks for an existing matching issue and, if found, links the customer to it as a new occurrence instead of creating…
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionSummarize issue + build search query
- ActionSearch Linear for matching open issueLinear
- LogicConfident duplicate match?
- ActionComment occurrence OR create new issueLinear
- OutputWrite Linear URL back to IntercomIntercom
What it does
Stops duplicate bug tickets. When an Intercom conversation is tagged as a bug, the workflow searches Linear for an existing open issue describing the same problem. If a strong match exists, it appends the new customer occurrence as a comment and bumps a count instead of opening a fresh issue; only genuinely new bugs become new Linear issues.
When to use it
Use when a single bug generates a flood of support tickets and your Linear board fills with near-identical issues. Consolidating occurrences gives engineers an accurate signal of how many customers are affected.
How it works
- 1An Intercom conversation is tagged `bug`, firing the trigger.
- 2The agent summarizes the issue and derives a search query.
- 3It searches Linear for open issues matching the symptom and area.
- 4A logic step decides: confident match versus no match.
- 5On a match, it comments the new customer, conversation link, and timestamp onto the existing issue.
- 6On no match, it creates a new scoped Linear issue.
- 7Either way, the resolved Linear URL is written back to the Intercom conversation as a note.
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.