Escalated Case Alert to Teams Channel

Overview

This flow monitors Salesforce for high-priority and escalated support cases on a recurring schedule, then posts formatted alert cards to a designated Microsoft Teams channel. It enables support teams to stay on top of critical cases without constantly checking Salesforce.

Use Case

Support operations teams need real-time visibility into escalated cases. Rather than relying on reps to manually flag critical issues, this flow automatically polls Salesforce every 15 minutes, identifies cases matching the configured priority threshold or escalation flag, and pushes a rich alert into a Teams support channel with all the key details.

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.

Import the solution

Import FlowLibsEscalatedCaseAlertDemo into your target environment.

Update environment variables

Set flowlibs_TeamsGroupId and flowlibs_TeamsChannelId to your target Teams team/channel. Adjust flowlibs_EscalatedCasePriority if your Salesforce org uses different priority labels.

Authorize connections

Open each connection reference and sign in with appropriate credentials for Salesforce and Microsoft Teams.

Adjust polling frequency

Edit the Recurrence trigger interval if 15 minutes is too frequent or infrequent for your use case.

Customize the filter

Modify the $filter parameter on the Salesforce action to match your case escalation criteria (e.g., add status filters, date range filters).

Turn on the flow

Set the flow state to On once connections are authorized and environment variables are configured.

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.

Priority eq '@{variables('varEscalatedPriority')}' or IsEscalated eq true

@{items('For_Each_Escalated_Case')?['CaseNumber']}

@parameters('flowlibs_TeamsGroupId')