PagerDuty Post-Incident Review Generator

Overview

This flow turns every resolved PagerDuty incident into a ready-to-edit postmortem. When an incident transitions to resolved, the flow pulls the full incident record and its responder notes, computes the timeline and reliability metrics (time-to-acknowledge / time-to-resolve), populates a branded Word post-incident-review (PIR) template, files the document into a SharePoint library, schedules a review meeting on the team calendar (Outlook), and posts a draft summary to the team in Teams - all stamped with a single correlation id.

Why it matters: PIRs are high value but tedious to start. Auto-generating a populated draft with the real timeline removes the blank-page friction and makes blameless reviews routine. Built as a demo - ships Off. Going live requires only connection authorization plus environment-variable configuration (no logic changes).

Use Case

An SRE / IT-Operations team runs post-incident reviews and wants a pre-filled PIR document, an archived copy, a scheduled review meeting, and a team notification created automatically the moment a PagerDuty incident resolves. Primary audience: IT Admins, Operations. Skill level: Advanced. Category: Document Management.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
PagerDuty	shared_pagerduty	OnIncidentResolved GetIncidentById GetIncidentNotes
Word Online (Business)	shared_wordonlinebusiness	CreateFileItem
SharePoint	shared_sharepointonline	CreateFile
Office 365 Outlook	shared_office365

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

AI-drafted analysis

Add Azure OpenAI to draft a summary and contributing-factors section from the notes/timeline before populating the template.

Severity gate

Add a Condition after Compose Incident to only generate PIRs for high-urgency incidents and skip the rest.

Action items

Create follow-up tasks in Planner or Azure DevOps from the review and link them back into the document.

Real Teams meeting

Swap the Outlook calendar event for Teams CreateTeamsMeeting (or set item/isOnlineMeeting) to attach a join link.

Distribution

Add the reviewers / stakeholders as Outlook email recipients with the document attached.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@coalesce(body('Get_Incident_Details')?['incident'], triggerOutputs()?['body'])

@if(equals(outputs('Compose_Acknowledged_At'),''),'N/A',string(div(sub(ticks(outputs('Compose_Acknowledged_At')),ticks(outputs('Compose_Triggered_At'))),600000000)))

@string(div(sub(ticks(outputs('Compose_Resolved_At')),ticks(outputs('Compose_Triggered_At'))),600000000))

@if(empty(body('Select_Responders')),'No responders acknowledged this incident.',replace(replace(replace(string(body('Select_Responders')),'"},{"name":"',', '),'[{"name":"',''),'"}]',''))

@{concat(formatDateTime(addDays(utcNow(),int(parameters('EnvVar_PIRReviewLeadDays'))),'yyyy-MM-dd'),'T16:00:00')}

Customize & download