DEVOPS
PagerDuty Resolved Incident to Postmortem Stub in Confluence
When a PagerDuty incident resolves, the workflow drafts a postmortem stub in Confluence pre-filled with the timeline, responders, and duration.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolvedPagerDuty
- ActionPull timeline, responders, and durationPagerDuty
- LogicBranch on whether postmortem is warranted
- ActionCreate pre-filled Confluence postmortem stubConfluence
- OutputPost draft link to Slack with owner promptSlack
What it does
When a PagerDuty incident is resolved, this workflow assembles the facts while they're fresh and drafts a postmortem stub in Confluence. The page is pre-filled with the incident timeline, who responded, time-to-resolve, and linked alerts, leaving the team to fill in only the analysis. It then nudges the channel so the writeup actually happens.
When to use it
Use it when postmortems get skipped because starting from a blank page is friction, and the timeline details fade once the incident closes. Best for teams that owe postmortems on significant incidents and want a consistent template populated automatically.
How it works
- 1A PagerDuty incident transitions to resolved and fires the workflow.
- 2The workflow pulls the incident timeline, responders, log entries, and total duration.
- 3A branch checks whether the incident was high enough urgency to warrant a postmortem.
- 4For qualifying incidents, it creates a Confluence page from the postmortem template, pre-filling timeline, responders, and duration.
- 5It posts the draft postmortem link to the team's Slack channel with an owner prompt.
- 6The final step records the page link back on the PagerDuty incident for traceability.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 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.