Opportunity Stage Change Pipeline Notifier

Overview

The Opportunity Stage Change Pipeline Notifier keeps sales teams and executives in lockstep with pipeline movement without requiring them to live inside Salesforce. On a recurring schedule (hourly), the flow queries Salesforce for opportunities whose stage changed within the last hour, formats a digest message for each one, and posts it to a designated Microsoft Teams sales channel. Each post highlights the deal name, the stage transition (old stage to new stage), the deal amount, and the expected close date so that anyone scanning the channel can see momentum at a glance.

The flow uses a scheduled trigger, a Salesforce records query, and a Teams post action. It is built to be configuration-driven via environment variables: the target Teams group and channel, the Salesforce stage-change lookback window, and the message template are all surfaced as settings so the same solution can be re-targeted at a different region, team, or sandbox tenant without editing the flow.

Use Case

Sales leaders frequently want a real-time pulse on pipeline movement but do not want to give every executive a Salesforce seat or train them to build dashboards. Posting stage transitions into a Teams channel meets people where they already collaborate, surfaces deals that have advanced (or slipped) in the last hour, and gives sales managers a low-friction prompt to congratulate reps or jump on at-risk opportunities. The flow also reduces noise from Salesforce-native notifications by consolidating multiple updates into a single hourly stream.

The flow is ideal for teams that:

• Sales teams that want lightweight pipeline visibility inside Microsoft Teams
• Executives who track deal momentum but do not work directly in Salesforce day-to-day
• Revenue operations groups that need a consolidated, low-noise stream of stage changes
• Organizations standardizing on Teams as the sales war-room collaboration surface

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.

Adjust the lookback window to match your run cadence

If you change the recurrence from hourly to every 15 minutes or to daily, update flowlibs_LookbackHours (or convert it to minutes) so the Salesforce query window aligns with the run frequency. Mismatched values cause either duplicate notifications or missed stage changes.

Filter to specific stages or deal sizes

Extend the Salesforce Get records filter to only fire on material moves (for example, transitions into Closed Won or Closed Lost, or opportunities above a minimum amount) to keep the Teams channel signal-to-noise high.

Route different segments to different channels

Promote the target channel to a lookup keyed on Salesforce region, business unit, or owner. Replace flowlibs_TeamsChannelId with a switch or a SharePoint config list so enterprise, mid-market, and SMB pipelines each land in their own channel.

Add an adaptive card with deep links

Swap the plain Teams post for an adaptive card that includes a 'Open in Salesforce' button (https://your-tenant.lightning.force.com/lightning/r/Opportunity/<Id>/view). This shortens the click path for managers who want to inspect the deal.

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, int(parameters('flowlibs_LookbackHours'))))

formatNumber(items('Apply_to_each')?['Amount'], 'C0', 'en-US')

formatDateTime(items('Apply_to_each')?['CloseDate'], 'MMM dd, yyyy')