TICKET MANAGEMENT
Triage a Sentry crash spike in Slack before filing a ticket
When a Sentry issue spikes past a threshold, post a triage card to Slack showing whether a matching Linear issue already exists, and let an engineer attach, file new, or dismiss…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry metric-alert (spike threshold) webhookSentry
- ActionSearch Linear for candidate duplicateLinear
- OutputPost interactive triage card to SlackSlack
- LogicBranch on engineer click: attach / create / dismiss
- ActionComment on or create Linear issueLinear
- OutputUpdate Slack card with outcomeSlack
What it does
Puts a human in the loop for high-volume crashes. Instead of auto-filing, it surfaces a spiking Sentry error in Slack alongside the likely duplicate, so an engineer decides whether to link, create, or ignore.
When to use it
When auto-creation has burned you with noise, or for severe spikes where you want a fast human judgment call rather than a silent ticket. Good for on-call rotations that live in Slack.
How it works
- 1Sentry fires a metric-alert webhook when an issue crosses an events-per-minute threshold.
- 2The flow searches Linear for a candidate duplicate by fingerprint.
- 3It posts an interactive Slack message: error summary, spike rate, affected release, and the best-match Linear issue (or none).
- 4The engineer clicks Attach, Create new, or Dismiss.
- 5Branch on the click: Attach comments the spike onto the matched Linear issue; Create opens a new Linear issue seeded with breadcrumbs and the Sentry link.
- 6The Slack card updates in place to show the resulting Linear issue and who actioned it.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.