Webex Meeting Quality Alert

Overview

This flow proactively catches Webex conferencing problems. On an hourly schedule it pulls recent meetings and their per-participant quality metrics (latency, packet loss, jitter) from the Webex REST API, flags any meeting that breaches the configured thresholds, logs a deduped incident to Dataverse, and alerts the IT/AV team in both Microsoft Teams and Outlook.

Why it matters: Poor call quality erodes productivity and is usually noticed too late. A scheduled quality sweep surfaces problem patterns (a host, a network, a device) for proactive fixes, with a durable Dataverse audit trail.

Connector note: The Webex Power Automate connector (shared_webex) is messaging-only — it has no meetings or meeting-quality operations. Meeting and quality data is therefore retrieved with the built-in HTTP action against the Webex REST API (/meetings and /meeting/qualities), authenticated with a Bearer token from the flowlibs_WebexAccessToken environment variable. Teams, Outlook, and Dataverse all use their connector actions.

Use Case

An IT/AV team wants early warning of recurring Webex quality issues, with the data to pinpoint the cause. Each hour the flow scans meetings that ended in the lookback window, evaluates each participant's audio/video metrics against thresholds, and raises one alert per affected meeting (idempotent — it will not re-alert a meeting already logged).

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord

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.

Tune thresholds

Adjust the latency/packet-loss/jitter env vars to your network's tolerances; no flow edits needed.

Match the Webex response shape

The quality field paths (latency, packetLoss, jitter) are written for a flat per-participant shape; adjust them if your Webex Meeting Qualities response nests metrics under audio/video resource arrays.

Scan frequency / window

Change the Recurrence interval and flowlibs_WebexQualityLookbackHours together to control coverage vs. cost.

Site rollup

Aggregate incidents by site/network to find the culprit; chart over time in Power BI.

Ticketing

Open a ServiceNow/Jira ticket on recurring incidents (a connector action could be added in the True branch).

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.

@{addHours(utcNow(), mul(-1, variables('varLookbackHours')))}

@or(greater(int(coalesce(item()?['latency'],0)),variables('varLatencyThreshold')),or(greater(float(coalesce(item()?['packetLoss'],0)),variables('varPacketLossThreshold')),greater(int(coalesce(item()?['jitter'],0)),variables('varJitterThreshold'))))

@greater(length(body('Filter_Poor_Quality_Participants')), 0)

@equals(length(coalesce(body('Check_Existing_Incident')?['value'],json('[]'))), 0)

flowlibs_meetingid eq '@{items('Apply_To_Each_Meeting')?['id']}'

Customize & download