TICKET MANAGEMENT
Route New Intercom Conversations to Deduped Linear Issues
On each new Intercom conversation, matches it against existing issue themes and either appends it to a known Linear issue as a +1 or opens a fresh, deduplicated Linear issue.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom conversation createdIntercom
- ActionEmbed summary and find nearest themePostgres
- LogicBranch on dedupe similarity threshold
- ActionComment +1 on existing Linear issueLinear
- ActionElse create new Linear issueLinear
- OutputTag conversation with Linear keyIntercom
What it does
Keeps your Linear backlog clean by ensuring every customer report maps to a single canonical issue. Repeat reports increment a counter instead of spawning duplicate tickets.
When to use it
Use it when support keeps filing the same bug under slightly different titles and product can't tell which issue is actually hot. This gives each problem one Linear issue with an accurate report count.
How it works
- 1An Intercom webhook fires when a new conversation is created.
- 2The flow embeds the conversation summary and queries Postgres for the nearest existing theme fingerprint.
- 3A branch checks whether similarity clears the dedupe threshold.
- 4If it matches a known theme, the flow finds the linked Linear issue and posts a comment with the new conversation link, then increments the report count.
- 5If no match clears the threshold, it creates a new Linear issue, stores the theme fingerprint and Linear issue ID in Postgres, and links the conversation.
- 6The Intercom conversation is tagged with the resolved Linear issue key for agent visibility.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.