TICKET MANAGEMENT
Correlate Intercom bug reports with Sentry errors before deduplicating into Linear
When a bug-tagged Intercom conversation comes in, this matches it against recent Sentry issues by symptom, attaches the stack trace and event count.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionExtract error signature with OpenAIOpenAI
- ActionMatch against recent Sentry issuesSentry
- LogicFingerprint and find existing Linear issueLinear
- ActionCreate or increment enriched Linear issueLinear
- OutputPost Linear and Sentry links to IntercomIntercom
What it does
Bridges what customers say with what your error tracking sees. A vague "the page crashed" report gets matched to the real Sentry issue, so the deduplicated Linear ticket carries the stack trace, error frequency, and a Sentry link, not just a customer paraphrase.
When to use it
Use it when your stack reports to Sentry and you want engineering-ready bugs: every escalation should already point at the underlying exception and its event volume, with customer reports deduplicated on top.
How it works
- 1An Intercom conversation tagged `bug` fires the trigger.
- 2OpenAI extracts the symptom, error text, and affected feature from the transcript.
- 3The flow queries Sentry for recent issues matching that signature and pulls the top candidate's stack trace and event count.
- 4It fingerprints the combined report and searches Linear: if a matching issue exists it increments the reporter count and refreshes the Sentry stats; otherwise it creates one enriched with the stack trace and Sentry link.
- 5It posts the Linear issue and matched Sentry link back to the Intercom conversation.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SentryErrors, performance, releases.
- 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
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.