AI AGENTS
Post-Incident Runbook Builder from PagerDuty Resolutions
When a PagerDuty incident resolves, the agent correlates it with its Sentry issue, drafts a structured post-incident runbook section, opens a GitHub PR.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolvedPagerDuty
- ActionFetch incident timeline and linked Sentry issueSentry
- ActionAgent synthesizes structured runbook section
- ActionCreate or update runbook in GitHub repoGitHub
- ActionOpen doc PRGitHub
- OutputPost summary to incident Slack channelSlack
What it does
This closes the doc gap at the incident level rather than the error level. When PagerDuty marks an incident resolved, the agent pulls the linked Sentry issue, reconstructs the timeline and root cause, and drafts a structured runbook entry — detection signal, triage steps, fix, and prevention. It opens a GitHub PR and drops a summary into the incident's Slack channel.
When to use it
Ideal for teams that run formal incident response through PagerDuty and want every resolved incident to leave behind a reusable runbook, not just a closed ticket.
How it works
- 1PagerDuty triggers when an incident is resolved.
- 2The agent fetches the incident timeline and follows the link to the originating Sentry issue for stack and breadcrumb context.
- 3It synthesizes detection, triage, fix, and prevention into a structured runbook section.
- 4It checks GitHub for an existing runbook for this service and either creates or updates it.
- 5It opens the doc PR and posts a concise summary into the incident's Slack channel for responders to confirm accuracy.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SentryErrors, performance, releases.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.