TICKET MANAGEMENT
Bundle repeated Intercom bug reports into one deduplicated Linear issue
When a support agent tags an Intercom conversation as a bug, this fingerprints the report and either opens a new Linear issue or increments a reporter count on the matching…
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionFingerprint the report with OpenAIOpenAI
- LogicSearch Linear for matching fingerprintLinear
- LogicBranch: existing issue vs. new issue
- ActionIncrement count or create Linear issueLinear
- OutputPost issue link back to Intercom as a noteIntercom
What it does
Turns a stream of look-alike bug reports into a single Linear issue with an accurate "reported N times" count. Instead of engineering wading through fifty tickets that are all the same crash, they get one issue that grows in priority as more customers hit it.
When to use it
Use it when your support team triages in Intercom and you want every confirmed bug to land in Linear without manual dedup. Best for teams where the same defect surfaces across many conversations before a fix ships.
How it works
- 1A support agent applies the `bug` tag to an Intercom conversation, firing the trigger.
- 2OpenAI reads the conversation transcript and produces a normalized fingerprint: a short canonical title plus a stable hash of the symptom, ignoring customer-specific wording.
- 3The flow searches Linear for an open issue carrying that fingerprint.
- 4If a match exists, it increments the reporter count in the issue body and appends the new conversation link; if not, it creates a fresh Linear issue stamped with the fingerprint.
- 5It writes the resulting Linear issue URL back onto the Intercom conversation as a note so the agent can reply with status.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.