TICKET MANAGEMENT
Enrich Intercom bug reports with logs before filing to Linear
For Intercom conversations classified as reproducible bugs, pulls the customer's recent error events from Sentry, attaches them to a Linear issue.
How it runs
The automated pipeline, trigger to output.
- TriggerConversation classified reproducible-bugIntercom
- ActionQuery Sentry for the customer's error eventsSentry
- ActionCreate enriched Linear issue with tracesLinear
- LogicCheck severity
- ActionPage on-call for high severityPagerDuty
- OutputWrite Linear link back to IntercomIntercom
What it does
Goes beyond classification: once a conversation is confirmed a reproducible bug, it correlates the customer to their recent Sentry error events and files a Linear issue enriched with stack traces and event counts. High-severity bugs additionally page on-call so regressions don't sit in a backlog.
When to use it
When your engineers reject bug tickets that lack technical evidence, and you want every promoted bug to arrive with real telemetry attached and the urgent ones routed to on-call immediately.
How it works
- 1An Intercom conversation classified `reproducible-bug` triggers the flow (trigger).
- 2The customer's identifier and time window are extracted from the conversation.
- 3Sentry is queried for matching error events and stack traces.
- 4A Linear issue is created with the repro steps plus the attached Sentry events and counts.
- 5A branch checks severity.
- 6If high severity, on-call is paged via PagerDuty with the Linear link.
- 7The Linear URL is written back to the Intercom conversation.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect SentryErrors, performance, releases.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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
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.