PagerDuty On-Call Schedule Digest

Overview

This flow publishes a clear, current on-call roster from PagerDuty every morning. It reads who is currently and next on call across the configured schedules, detects any coverage gaps, formats an HTML roster card, and posts it to a Teams channel and emails it to the team distribution list.

Why it matters: People waste time figuring out who to page during an incident. A daily, current roster posted where the team already works removes the guesswork and surfaces unfilled shifts before they cause a missed page. Built and verified (Flow Checker 0 errors / 0 warnings). Ships Off - going live requires only authorizing the connections and setting the environment variable values.

Use Case

A team running multiple PagerDuty schedules wants one current view of who is on call (and who is next), posted where everyone already works, with explicit warnings about schedules that have no coverage in the window.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
PagerDuty	shared_pagerduty	GET /oncalls
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

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.

Shift-change ping

Add a second Recurrence near handoff time, or a Teams DM to the incoming on-call person.

Per-schedule display names

The roster already shows schedule.summary; group rows by schedule or sort by start time as needed.

Holiday awareness

Flag on-call windows that fall on company holidays before posting.

Escalation context

The roster includes the escalation level; extend it to list the full escalation policy via GET /oncalls?include[]=escalation_policies.

Mobile push

Add a Power Automate / Power Apps notification for field staff who are not in Teams.

Swap to a connector action

If PagerDuty publishes an on-call connector operation, replace Get OnCall Roster (HTTP) with it; nothing downstream changes.

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.

@concat(variables('varPdApiBase'), '/oncalls?time_zone=UTC&earliest=true&include[]=users&include[]=schedules&since=', utcNow(), '&until=', addDays(utcNow(), int(variables('varLookAhead'))), '&schedule_ids[]=', join(split(variables('varScheduleIds'), ','), '&schedule_ids[]='))

@not(contains(outputs('Compose_OnCalls_String'), trim(item())))

<tr><td>@{coalesce(item()?['schedule']?['summary'],'(unknown schedule)')}</td><td>@{coalesce(item()?['user']?['summary'],'(unfilled)')}</td><td>@{formatDateTime(coalesce(item()?['start'],utcNow()),'MMM dd HH:mm')} - @{if(empty(item()?['end']),'ongoing',formatDateTime(item()?['end'],'MMM dd HH:mm'))}</td><td>@{coalesce(item()?['escalation_level'],'')}</td></tr>

@body('Get_OnCall_Roster')?['oncalls'][0]?['user']?['summary']

Customize & download