TICKET MANAGEMENT
Enrich Intercom bug with Sentry traces and recent GitHub commits
Files a Linear bug from a tagged Intercom thread and enriches it with matching Sentry error events and the GitHub commits that touched the affected area.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'bug'Intercom
- ActionExtract symptom, area, timestamp
- ActionSearch Sentry for matching error eventsSentry
- ActionList recent GitHub commits in affected pathGitHub
- LogicEvidence relevant enough to attach?
- ActionCreate enriched Linear issueLinear
- OutputPost Linear link as Intercom noteIntercom
What it does
Creates a richly-scoped Linear bug from an Intercom conversation, then attaches likely-cause evidence. It searches Sentry for error events matching the reported symptom and time window, and pulls recent GitHub commits touching the suspected files or service, so the Linear issue arrives with both customer impact and a starting point for the fix.
When to use it
Use when your support-to-engineering loop is slow because engineers have to manually hunt for the stack trace and the commit that broke things. This front-loads that investigation onto every bug it files.
How it works
- 1An Intercom conversation tagged `bug` fires the trigger.
- 2The agent extracts the symptom, affected area, and approximate timestamp from the thread.
- 3It queries Sentry for matching error events and grabs the top stack traces.
- 4It lists recent GitHub commits touching the implicated path or service.
- 5A logic step ranks whether the Sentry/commit evidence is relevant enough to attach.
- 6A Linear issue is created with the scope, linked Sentry events, and candidate commits.
- 7The Linear URL is posted back to the Intercom conversation as an internal note.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SentryErrors, performance, releases.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 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.