You are here:
Equivalent Features in Flows and Workflow Rules
Features and fields in workflow rules correspond to certain things in flows. Use the equivalent features and fields to build flows that can replace your workflow rules.
Required Editions
| View supported editions. |
General
| Workflow Rules | Flows |
|---|---|
| Create New Rule | When creating a flow, select Record-Triggered Flow. |
| Description | Use the Description field. The field is available when saving the flow. |
| Email Alerts | Use the Action element. |
| Outbound Messages | Use the Action element. |
| Rule Name | Use the Flow Label field. The field is available when saving the flow. |
| Select Object | Use the Object field. The field is available in the Start element, in the Select Object section. |
| Tasks | Use the Create Records element. For How to Set the Record Fields, select Use separate resources, and literal values and then select the Task object. |
| Time Triggers | Use a scheduled path. To create a scheduled path, in the Start element, optimize the flow for Actions and Related Records. Then, from the flow canvas, select Add Scheduled Path on the Start node. |
Evaluation Criteria
In flows, evaluation criteria are defined in the Start element, in the Set Entry Conditions section.
| Workflow Rules | Flows |
|---|---|
| created | Trigger the Flow When:
|
| created, and any time it's edited to subsequently meet criteria | Trigger the Flow When: When to Run the Flow for Updated Records:
|
| created, and every time it's edited | Trigger the Flow When: When to Run the Flow for Updated Records:
|
To manually convert workflow rules with unsupported use cases in entry criteria, create a Decision element inside the Flow. Then recreate the workflow rule steps with the condition builder.
Rule Criteria
In flows, rule criteria are defined in the Start element, in the Set Entry Conditions section.
| Workflow Rules | Flows |
|---|---|
| Run this rule if the criteria are met | For Condition Requirements, select All Conditions Are Met (AND) |
| Run this rule if the formula evaluates to true | For Condition Requirements, select Formula Evaluates to True |
Field Updates
In flows, field updates are done using the Update Records element. In the Update Records element, for How to Find Records to Update and Set Their Values, select Use the {object name} record that triggered the flow. In flows, you can enter values directly, or use formulas or references for field values. You can also update multiple fields in a single flow. To improve performance, place field updates in a flow optimized for fast field updates (before-save).
Flows don’t support field update notifications for the Owner field.
A Get Records element can be required to reference certain elements, like users or groups.
Task Fields
To create a task in a flow, use the Create Records element.
| Workflow Rules | Flows |
|---|---|
| Assigned To |
|
| Comments |
|
| Due Date |
|
| Object |
|
| Priority |
|
| Protected Component | N/A |
| Status |
|
| Subject |
|
| Unique Name | N/A |
Operators
Flow Builder shows only the operators that are relevant to the field. Less Than, Greater Than,
Less Than or Equal, and Greater Than or Equal, appear only for number fields.
| Workflow Rules | Flows |
|---|---|
does not contain
|
N/A |
equals
|
Equals
|
excludes
|
N/A |
greater or equal
|
Greater Than or Equal (only number
fields) |
greater than
|
Greater Than (only number fields) |
includes
|
N/A |
less or equal
|
Less Than or Equal (only number fields) |
less than
|
Less Than (only number fields) |
| N/A |
Ends With
|
| N/A |
Is Null
|
| N/A |
Is Changed
|
not equal to
|
Does Not Equal
|
starts with
|
Starts With
|
within
|
N/A |
To manually convert workflow rules that use the does not contain operator, use custom condition logic. For
example, create a condition that uses the Contains
operator in the first condition, and in the condition logic, enter NOT
1.
