TICKET MANAGEMENT
Cluster inbound crash reports and page on a surging umbrella bug
Accepts crash reports on a webhook, clusters each one to an umbrella bug by stack signature, updates the affected-user count.
How it runs
The automated pipeline, trigger to output.
- TriggerCrash report received on webhookHTTP webhook
- ActionMatch stack signature to umbrella (create if new)Postgres
- ActionRecord affected user + recount clusterPostgres
- LogicBranch: crossed paging threshold?
- OutputOpen PagerDuty incident for surging umbrellaPagerDuty
What it does
Ingests raw crash payloads from any source over a webhook, assigns each to the correct umbrella bug by its normalized stack signature, and keeps a live affected-user count per cluster. When a cluster's impact spikes past your threshold, it pages the on-call engineer.
When to use it
Use it when crashes arrive from a custom client, SDK, or third-party tool that does not integrate with your tracker directly. It gives you clustering and alerting without routing everything through Sentry first.
How it works
- 1A crash report arrives on the webhook.
- 2The flow normalizes the stack trace into a signature and looks up its umbrella in Postgres, creating a new umbrella row if none exists.
- 3It records the user as affected and recomputes the cluster's unique-user count.
- 4A branch checks whether the count crossed the paging threshold within the window.
- 5If it did, it triggers a PagerDuty incident with the umbrella summary and a link; otherwise it ends quietly.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.