TICKET MANAGEMENT
Suppress duplicate PagerDuty pages for an already-tracked crash
When PagerDuty triggers an incident, it checks whether the crash signature already has an open canonical bug and, if so, auto-resolves the page with a link instead of waking…
How it runs
The automated pipeline, trigger to output.
- TriggerNew PagerDuty incidentPagerDuty
- ActionMatch signature to canonical bugPostgres
- LogicBranch: tracked-and-open vs. novel
- ActionAuto-resolve page with Linear linkPagerDuty
- OutputLog suppression for noise reportPostgres
What it does
Stops a known, already-ticketed crash from re-paging on-call. Incoming PagerDuty incidents are matched against the registry of crash signatures that already map to an open canonical bug; matches get auto-resolved with a note, while genuinely new signatures escalate normally.
When to use it
When a single recurring defect generates repeated alerts overnight and your on-call rotation is burning out acknowledging the same incident. Use it to page only on novel signatures until the canonical bug is fixed.
How it works
- 1A new PagerDuty incident triggers the flow with its alert payload and dedup key.
- 2The flow extracts the crash signature and queries the Postgres registry for an open canonical ticket.
- 3If a tracked, unresolved canonical bug exists, it auto-resolves the PagerDuty incident with a comment linking the Linear ticket and increments the occurrence count.
- 4If the signature is new or its canonical bug is already closed, it leaves the incident active so escalation proceeds.
- 5It logs every suppression to Postgres for an on-call noise report.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.