---
schema_version: "1"
id: 84d0d15ff29888408a030b009b861ed4b4aa0def697c66f4979e62d1c2d74f5b
title: Opportunity Management Process Example
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_example.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_example.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 64295ac67623d1ac12bbfe9a084b8bf54696b6ed46d84079f378b1b547bf9948
description: This example automates a single business process by using the Process Builder instead of workflow rules.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Opportunity Management Process Example

This example automates a single business process by using the Process Builder instead of workflow rules.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>) and Lightning Experience</td></tr><tr class="" id="process_example__d4862e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_example__d4862e347"><a name="process_example__d4862e347"></a><strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</span></td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").

The example demonstrates how you can use the Process Builder to automate a single process by adding multiple groups of criteria and then associating individual actions with those criteria. In addition, some actions are available with the Process Builder that you can’t perform with workflow rules, such as creating records.

In this example, the process is defined to start when an opportunity record (1) is created or edited.

Three criteria nodes are then set up to check whether a high-value deal was won (2), a high-value deal was lost (3), or a quote was given (4). For the first criteria node that evaluates to true, the associated action group is executed.

![Screenshot of example process](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/process_builder/pb_example.png)

The High Value Deal Won criteria checks whether the opportunity’s stage is closed and won and also whether the opportunity’s amount is greater than $1,000,000.00. If both of these conditions are met, the associated action group is executed. For this criteria node, three immediate actions (5) and one scheduled action (6) are defined.

These actions:

- Create a draft contract record that's associated with the opportunity’s account.
- Congratulate the opportunity owner for closing and winning the opportunity by posting to the Sales Chatter group.
- Notify the VP of sales via email that the opportunity was closed and won.
- Create a high priority follow-up task for the associated account’s owner, which is scheduled to execute six days after the opportunity’s Close Date.

If the High Value Deal Won criteria conditions aren’t met, the associated group of actions doesn’t execute and the next criteria node (High Value Deal Lost) is evaluated.

The High Value Deal Lost criteria node checks whether the opportunity stage is closed and lost and whether the opportunity amount is greater than or equal to $1,000,000.00. If these conditions are true, we’ve set up an action (7) to notify the VP of sales by creating a chatter post on the opportunity record. The post identifies the opportunity and the opportunity amount that was lost.

If neither of the previous criteria conditions are met, the next criteria node defined in this process checks whether the opportunity stage is set to “Proposal/Quote Given.” If this condition is true, a scheduled action (8) is executed three days after the record is updated. The scheduled action creates a follow-up task for the opportunity owner to call to inquire about the opportunity.

Using the Process Builder, we’ve combined three criteria nodes and associated actions into a single, automated process. To automate the same business process with workflow, you would have to create three different workflow rules and use Apex triggers to create the contract record and post to the Sales Chatter group.