Approval-Driven Salesforce Status Update

Overview

This flow implements an approval-gated Salesforce record update pattern. When triggered manually with a Salesforce record ID and approval details, it routes an approval request to a configured approver. Based on the approval outcome, it updates the Salesforce record's status/stage field to either the approved or rejected value, then posts a confirmation message to a Teams channel.

Use Case

Discount approvals, contract terms changes, opportunity stage gates, or any scenario where a Salesforce field update requires human sign-off before proceeding.

The flow is ideal for teams that:

• Sales teams that need manager sign-off on discounts before updating opportunity stages
• Operations teams gating contract terms changes behind a formal approval
• Any team that wants an auditable, Teams-notified approval step before mutating a Salesforce record

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Approvals	shared_approvals	StartAndWaitForAnApproval (Sends a Basic approval and blocks until the assignee responds.)
Salesforce	shared_salesforce	PatchItem_V3 (Updates the configured status field on the target Salesforce record.)
Microsoft Teams	shared_teams	PostMessageToConversation (Posts approved/rejected notification to the configured Teams channel.)

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.

Swap the Salesforce object and status field

Change flowlibs_SalesforceObjectType (e.g., from Account to Opportunity or Case) and flowlibs_SalesforceStatusField together (e.g., StageName, Status, custom__c) so the same flow can drive approvals across any SObject without editing the actions.

Tune approved/rejected values per environment

Set flowlibs_SalesforceApprovedStatus and flowlibs_SalesforceRejectedStatus to your team's actual stage/status picklist values (e.g., 'Approved - Closed Won' / 'Lost - Discount Denied'). No flow edit required.

Route approvals to a group or shared mailbox

Update flowlibs_ApprovalAssignedToEmail to a distribution list, group email, or shared mailbox to fan the approval out to multiple potential approvers.

Point notifications at the right deal room

Set flowlibs_TeamsGroupId and flowlibs_TeamsChannelId to the team/channel that should see the outcome (e.g., a per-deal channel or a central Sales Ops channel).

Enrich the approval body

Edit the Start Approval action to include extra context (current SF stage, amount, account name) by adding a Get record action before Start Approval and concatenating fields into the details parameter.

Customize & download