TICKET MANAGEMENT
Collapse PagerDuty alert storms into one parent incident
On a new PagerDuty incident, clusters it with recent incidents sharing the same root signal and, when it belongs to an active storm, links it under a parent and suppresses…
How it runs
The automated pipeline, trigger to output.
- TriggerNew PagerDuty incident openedPagerDuty
- ActionNormalize payload into error signatureOpenAI
- ActionLook up active incidents in time windowPostgres
- LogicNew storm or member of existing storm?
- ActionLink under parent + suppress pagingPagerDuty
- OutputUpdate storm count in Slack channelSlack
What it does
When PagerDuty opens a new incident, the workflow checks whether it is part of an ongoing alert storm by comparing service, error signature, and timing against active incidents. Members of the same storm are linked under a single parent incident, and redundant pages are suppressed so the on-call sees one alert, not fifty.
When to use it
Use it during cascading failures where one root cause fires dozens of monitors. It cuts pager noise and gives responders a single thread to work.
How it works
- 1A new PagerDuty incident triggers the flow.
- 2OpenAI normalizes the alert payload into a stable error signature.
- 3Postgres looks up active incidents with matching signatures inside a time window.
- 4A logic step decides whether this is a new storm or a member of an existing one.
- 5If it joins a storm, PagerDuty links it under the parent and snoozes its notification.
- 6Slack updates the incident channel with the running duplicate count.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.