AI AGENTS
Post-Incident Postmortem Draft on PagerDuty Resolve
When a PagerDuty incident resolves, an agent assembles the timeline from PagerDuty and Slack, drafts a blameless postmortem.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolvedPagerDuty
- LogicFilter to postmortem-worthy incidents
- ActionCollect timeline + Slack threadSlack
- ActionAgent drafts blameless postmortem
- ActionFile draft Confluence pageConfluence
- OutputLink draft to commander in SlackSlack
What it does
Automates the tedious first draft of a postmortem. As soon as an incident is resolved, the agent pulls the incident timeline, the responder Slack thread, and the metric context, then writes a blameless postmortem covering impact, timeline, root cause, and follow-up actions. It files the draft for human editing rather than publishing.
When to use it
Use it after any significant incident so the writeup starts at 80% instead of a blank page. The incident commander refines and approves; the agent handles the grind of stitching the narrative together.
How it works
- 1A PagerDuty incident resolution triggers the flow.
- 2A logic step filters to incidents above a severity or duration threshold worth a postmortem.
- 3The agent collects the incident timeline and responder messages from the Slack channel.
- 4It drafts a structured blameless postmortem with timeline, root cause, and action items.
- 5The draft is filed as an unpublished Confluence page.
- 6A Slack message links the draft and asks the incident commander to review and publish.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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 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.
