Automated Opportunity Stage Advancement

Overview

This flow automates routine Salesforce CRM hygiene by advancing stale opportunities from one sales stage to the next on a scheduled cadence. It removes the need for sales reps or operations teams to manually nudge opportunities forward when they've sat untouched too long — a common source of pipeline data decay and missed forecasts.

The flow runs daily at 6:00 AM Eastern Time, queries open Salesforce opportunities sitting in a configurable "from" stage that haven't been modified in a configurable number of days, and moves them into a configurable "to" stage. All three of those values live in environment variables, so the behavior can be retargeted without touching the flow logic.

Use Case

Sales operations at a mid-size B2B company complained that opportunities in Proposal/Price Quote were routinely forgotten — reps would send quotes, the prospect would respond, but the stage would never get updated to Negotiation/Review. Forecasts were chronically wrong and the pipeline dashboard looked stuck.

This flow solves that by automatically promoting stale Proposal/Price Quote opportunities (unmodified for 7+ days, still open) into Negotiation/Review, giving reps a fresh trigger to review the deal. The same pattern works for any stage-to-stage progression — swap the environment variable defaults and redeploy.

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 which stages are advanced

Edit the flowlibs_SalesforceFromStage and flowlibs_SalesforceToStage env variable values in the target environment. No flow edit required. Example: set From=Qualification, To=Needs Analysis to automate early-funnel progression instead.

Change the staleness threshold

Edit flowlibs_SalesforceLookbackDays. The value is passed into SOQL's LAST_N_DAYS:N macro, so 14 means 'not modified in the last 14 days.'

Run more or less often

Edit the Run_Daily_At_6AM trigger recurrence. The flow is idempotent — running it twice in a day simply advances any newly-stale opportunities; already-advanced ones no longer match the From filter.

Add a notification

Insert a Teams/Outlook action after Compose_Run_Summary and use outputs('Compose_Run_Summary') as the message body.

Cap per-run volume

The SOQL query hard-codes LIMIT 100. Raise or lower this in the Query_Stale_Opportunities_Via_SOQL action if needed. For very large pipelines, consider pairing with an Apply-to-each concurrency of 5–10.

Filter by record owner or type

Extend the SOQL WHERE clause (e.g., AND RecordTypeId = 'XYZ' or AND OwnerId = :ownerId) to scope which opportunities are advanced.

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('SELECT Id, Name, StageName, LastModifiedDate FROM Opportunity WHERE StageName = ''',
variables('varFromStage'),
''' AND LastModifiedDate <= LAST_N_DAYS:',
variables('varLookbackDays'),
' AND IsClosed = false ORDER BY LastModifiedDate ASC LIMIT 100')}

@{concat('Opportunity stage advancement complete. ',
string(variables('varAdvancedCount')),
' opportunity(ies) moved from ''',
variables('varFromStage'),
''' to ''',
variables('varToStage'), '''.')}