DEVOPS
Auto-Draft Postmortem Stub When an Incident Resolves
When a PagerDuty incident resolves, pulls its timeline plus correlated Datadog metrics and drafts a pre-filled postmortem page in Confluence so the responder reviews instead…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolved webhookPagerDuty
- LogicSkip if below postmortem severity threshold
- ActionFetch incident timeline and respondersPagerDuty
- ActionPull Datadog metrics for the windowDatadog
- ActionDraft postmortem narrative with LLMOpenAI
- OutputCreate populated postmortem in ConfluenceConfluence
What it does
The moment a PagerDuty incident is marked resolved, this workflow assembles a postmortem stub: incident timeline, who acknowledged and resolved it, time-to-resolution, and the relevant Datadog metric snapshots around the spike. It writes all of that into a templated Confluence page so the team's writeup starts at 70% done.
When to use it
Use it when postmortems get skipped or written days late because nobody wants to reconstruct the timeline. Triggering at resolution captures the context while it is fresh and lowers the activation energy for a proper review.
How it works
- 1A PagerDuty webhook fires when an incident transitions to resolved.
- 2A logic step checks the incident's urgency or priority and skips low-severity noise below the postmortem threshold.
- 3Fetch the full incident timeline and responder actions from PagerDuty.
- 4Pull Datadog metrics for the affected service across the incident window.
- 5An LLM composes a draft narrative, contributing-factors list, and action-item placeholders.
- 6Create the populated postmortem page in Confluence and link it back on the incident.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.