TICKET MANAGEMENT
Deduplicate New PagerDuty Incidents into an Open Outage
When a new PagerDuty incident is created, checks whether an open incident already exists for the same service and recent window.
How it runs
The automated pipeline, trigger to output.
- TriggerNew PagerDuty incident createdPagerDuty
- ActionList open incidents for the same service in the lookback windowPagerDuty
- LogicBranch: matching open incident found?
- ActionMerge new incident into existing one as duplicatePagerDuty
- OutputPost consolidated update to incident Slack channelSlack
What it does
During an outage, the same failure often pages repeatedly, opening a swarm of near-identical PagerDuty incidents. This workflow catches each newly created incident, looks for an existing open incident on the same service within a short lookback window, and if one is found, merges the newcomer into it. The surviving incident stays the single source of truth and Slack gets one clean notification per real outage.
When to use it
Run this on any high-traffic PagerDuty service where flapping checks or fan-out alerting create duplicate incidents. It is most valuable for teams that page on every failed health check and end up acknowledging the same problem five times.
How it works
- 1A new incident is created in PagerDuty and fires the trigger.
- 2The flow queries PagerDuty for open incidents on the same service from the last lookback window.
- 3A branch checks whether a matching open incident exists.
- 4If yes, the new incident is merged into the existing one as a duplicate.
- 5A single consolidated update is posted to the incident's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.