ADO Pull Request Review Reminder

Overview

A scheduled demo cloud flow that monitors Azure DevOps pull request review queues using the Azure DevOps connector's HttpRequest action — a real connector call, not an inline fixture. The flow queries the ADO REST API for active pull requests, computes each PR's age using ticks-based arithmetic, filters for stale PRs exceeding a configurable hour threshold, then delivers an HTML digest email via Outlook and posts a summary alert to a Teams channel.

Use Case

Engineering teams lose velocity when pull requests sit idle in review queues. This flow automates the "stale PR" nudge by querying Azure DevOps for all active PRs, calculating their age in hours, and filtering those that exceed the configured threshold. The digest is sent to both email and Teams so project leads and developers stay aware of aging reviews. As a FlowLibs demo, the flow ships Off — turn it on after configuring the ADO connection, environment variables, and connection references for your tenant.

Flow Architecture

Environment Variables

Connectors & Connections

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.

Change the schedule

Edit the Recurrence trigger's frequency, interval, startTime, or timeZone.

Adjust staleness threshold

Update the flowlibs_PrStaleThresholdHours environment variable value. No flow edit required.

Point at a different ADO org or project

Update the flowlibs_AdoOrganization and flowlibs_AdoProject env vars.

Change digest recipient

Update the flowlibs_DigestRecipientEmail env var.

Filter by repository

Add &searchCriteria.repositoryId={repoGuid} to the ADO API URI in the Get Active Pull Requests action.

Add reviewer-level DMs

Insert a For Each loop after the Filter Array to iterate stale PRs and send individual Teams DMs to each reviewer's UPN from the parsed reviewers array.

Add escalation tier

Duplicate the If branch with a higher threshold (e.g., 72 hours) and post to a management channel.

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.

int(parameters('flowlibs_PrStaleThresholdHours'))

concat(variables('varAdoProject'), '/_apis/git/pullrequests?searchCriteria.status=active&api-version=7.0')

div(sub(ticks(utcNow()), ticks(item()?['creationDate'])), 36000000000)

greater(div(sub(ticks(utcNow()), ticks(item()?['creationDate'])), 36000000000), variables('varPrStaleThresholdHours'))

greater(length(body('Filter_Stale_Pull_Requests')), 0)

item()?['title'], item()?['repository']?['name'], item()?['createdBy']?['displayName'], item()?['_links']?['web']?['href']