TICKET MANAGEMENT
Reproduce Intercom Bugs and Link Matching Sentry Errors in Linear
On a new bug-flagged Intercom reply, an agent reproduces the issue, searches Sentry for the matching error signature.
How it runs
The automated pipeline, trigger to output.
- TriggerBug-flagged Intercom reply receivedIntercom
- ActionSummarize symptom and time windowOpenAI
- ActionAttempt reproduction in sandbox browserBrowserbase
- ActionSearch Sentry for matching errorSentry
- LogicBranch: Sentry match found?
- OutputFile Linear issue with linked Sentry eventLinear
What it does
Connects a customer's words to the actual exception. The agent reproduces the reported bug, then finds the corresponding Sentry event so the resulting Linear issue carries a real stack trace instead of a guess.
When to use it
Use it when many bug reports are actually surfacing known backend errors, and engineers waste time re-discovering a Sentry event that already exists. Ideal for production apps with active error monitoring.
How it works
- 1A bug-flagged customer reply arrives in Intercom and triggers the flow.
- 2The agent summarizes the symptom and the time window from the conversation.
- 3It attempts the reproduction in a sandbox browser and records the error text.
- 4It queries Sentry for events matching the message, route, and time window.
- 5A branch checks whether a Sentry match was found.
- 6A Linear issue is created with repro steps plus the linked Sentry issue URL, or flagged for manual triage when no match exists.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Connect SentryErrors, performance, releases.
- 5Connect LinearIssues, projects, cycles, triage.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.