TICKET MANAGEMENT
Detect Recurring PagerDuty Alerts and Open a GitHub Problem Issue
Records every PagerDuty incident, detects when the same alert signature recurs beyond your tolerance over a 30-day window.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- ActionLog alert signature and service to PostgresPostgres
- LogicCount signature recurrences over 30-day windowPostgres
- LogicWithin tolerance or issue exists -> exit
- ActionOpen GitHub problem issue with recurrence timelineGitHub
- OutputPost issue link to Slack channelSlack
What it does
Stops the same page from waking people up forever. Each PagerDuty incident is logged with its alert signature and service. When that signature recurs more than your allowed number of times in 30 days, the workflow opens a GitHub issue tagged `problem` containing the full recurrence timeline and links back to each individual incident.
When to use it
Use it when on-call keeps acknowledging the same flapping alert and the underlying defect never makes it onto an engineering backlog. Ideal for SRE and platform teams who want chronic noise converted into a tracked, prioritized fix automatically.
How it works
- 1A PagerDuty incident trigger fires the run.
- 2The incident's alert signature and service are written to a Postgres history table.
- 3A query counts recurrences of that signature in the last 30 days.
- 4If recurrences are within tolerance, the run ends.
- 5Over tolerance with no existing open issue, a GitHub problem issue is created with the recurrence timeline.
- 6A confirmation with the issue link is posted to the team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.