TICKET MANAGEMENT
Notify every Intercom reporter when their deduplicated Linear bug ships a fix
When a deduplicated Linear bug issue moves to Done, this reopens every Intercom conversation that fed into it and sends each reporter a personalized fix-shipped reply.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear bug issue moved to DoneLinear
- ActionRead linked Intercom conversation IDsLinear
- ActionDraft fix-shipped reply with OpenAIOpenAI
- ActionReopen and reply to each Intercom conversationIntercom
- OutputComment notification count on Linear issueLinear
What it does
Closes the loop after a fix ships. Because the dedup pipeline records every Intercom conversation attached to a bug, this workflow can tell all of those customers the bug is fixed in one motion, instead of leaving stale tickets that nobody ever followed up on.
When to use it
Use it when bugs were deduplicated into a single Linear issue and you want every affected customer to hear back the moment engineering closes it. Great for support teams that care about reopen-and-confirm hygiene.
How it works
- 1A Linear webhook fires when a bug-fingerprinted issue transitions to Done.
- 2The flow reads the list of linked Intercom conversation IDs stored on the issue during dedup.
- 3OpenAI drafts a warm, specific fix-shipped message referencing the original symptom, with one variant suitable for all reporters.
- 4For each linked conversation, the flow reopens it in Intercom and posts the personalized reply.
- 5It writes a closing comment back on the Linear issue noting how many customers were notified.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect IntercomConversations, contacts, articles.
- 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
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.
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…
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.
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.