Salesforce Flow helps administrators and developers automate business processes without writing large amounts of Apex code. However, even a well-designed Flow can create problems if it runs more often than necessary.
Imagine a record-triggered Flow that sends an email whenever an Opportunity is updated. If the email should only be sent when the Opportunity moves to the Proposal stage, running the Flow on every update can create unnecessary actions.
This is where Salesforce Flow entry criteria become important. They control which records qualify to trigger a Flow and help make automation more efficient and predictable.
What Are Salesforce Flow Entry Criteria?
Entry criteria are conditions configured in the Start element of a record-triggered Flow. They determine when a record meets the requirements for the Flow to run.
You can configure conditions using different options, including:
All Conditions Are Met (AND)
Any Condition Is Met (OR)
Custom Condition Logic
Formula Evaluates to True
Each option serves a different purpose. Choosing the right one helps prevent unnecessary automation and makes your Flow easier to understand.
- Use AND Conditions When Every Requirement Matters
The AND option runs the Flow when all configured conditions are satisfied.
For example, suppose your business wants to create a follow-up task when an Opportunity reaches the Proposal stage and its amount exceeds $10,000.
Your entry criteria could be:
Field
Operator
Value
Stage
Equals
Proposal
Amount
Greater Than
10000
With AND conditions, both requirements must be met.
This approach works well when an automation should run only for records that satisfy several business requirements.
Best practice: Add only the conditions needed to define the business process. Too many unnecessary conditions can make a Flow difficult to maintain.
- Use OR Conditions for Alternative Scenarios
Sometimes, a Flow should run when any one of several conditions is satisfied.
For example, a support team may want a notification when a Case becomes either High or Critical priority.
You could configure these conditions:
Field
Operator
Value
Priority
Equals
High
Priority
Equals
Critical
With the OR option, either condition can qualify the record.
However, there is an important detail for record-triggered Flows that run on updates: Salesforce evaluates whether the record transitions from meeting none of the entry conditions to meeting at least one. If the record already met one condition before the update, simply meeting another condition does not necessarily trigger the Flow again.
Understand this behavior before using OR conditions in automation that runs on record updates.
- Use Custom Condition Logic for Complex Requirements
Business requirements do not always fit a simple AND or OR structure.
Suppose an Opportunity should trigger a Flow when it is in the Proposal stage and either its amount or close date changes.
You could configure three conditions:
Stage equals Proposal.
Amount Is Changed equals True.
Close Date Is Changed equals True.
Then define the custom condition logic as:
1 AND (2 OR 3)
This means the Opportunity must be in the Proposal stage, and either the amount or close date must change.
Custom condition logic is useful when your business requirements involve a combination of conditions. Keep the logic readable and document why each condition is needed.
- Choose the Correct Update Trigger Behavior
One of the most important settings appears under When to Run the Flow for Updated Records.
Salesforce provides two main options when entry conditions are configured for a record-triggered Flow that runs on updates.
Every time a record is updated and meets the condition requirements
The Flow can run on every update when the record satisfies the conditions after the update, even if it satisfied them before.
Only when a record is updated to meet the condition requirements
The Flow runs when an update causes the record to transition from not meeting the requirements to meeting them.
Consider an Opportunity with a stage of Proposal.
If the Flow is configured to run only when the record is updated to meet the conditions, changing the Opportunity's description while it remains in the Proposal stage will not trigger the Flow again if the entry conditions were already satisfied.
This distinction is especially important for Flows that send notifications, create tasks, or initiate other actions that should not happen repeatedly.
- Avoid Unnecessary Flow Executions
Every unnecessary automation run can make troubleshooting more difficult and may contribute to additional processing.
Consider a Flow that updates an Account whenever any field changes, even though it only needs to run when the Account's customer category changes.
You can improve this design by defining more specific entry criteria.
For example:
Field
Operator
Value
Customer Category
Is Changed
True
This focuses the Flow on changes that matter to the business.
Be careful when using the Is Changed operator with Flows configured for both record creation and updates. A newly created record has no previous field value to compare, so a change-based condition alone may not behave as expected for creation.
If the Flow must run on creation as well as when a specific field changes, consider an appropriate formula using ISNEW() and ISCHANGED(), or separate the creation and update logic into different Flows.
- Keep Entry Criteria Simple and Maintainable
A Flow may work correctly today but become difficult to manage when more conditions are added.
To prevent this, use clear condition names, meaningful descriptions, and straightforward logic.
Follow these practices:
Use specific conditions that match the business requirement.
Avoid repeating the same logic unnecessarily.
Use formulas only when they make the requirements clearer.
Document complex condition logic.
Review existing automation before creating another Flow for the same object.
Also consider whether the Flow should run before or after the record is saved. Before-save Flows are useful for updating fields on the triggering record, while after-save Flows are suitable for actions involving related records and other business processes.
Entry criteria determine when the Flow qualifies to run; the Flow's trigger configuration determines the broader execution context.
- Test Entry Criteria With Different Record Scenarios
Testing only one successful scenario is not enough to confirm that your entry criteria work correctly.
Create test cases for records that meet the conditions, records that do not meet them, and records that already satisfied the conditions before an update.
For example, if your Flow should create a task when an Opportunity enters the Proposal stage, test these situations:
Scenario
Expected Result
New Opportunity created in Proposal stage
Flow runs if the configured criteria are satisfied
Opportunity changes from Qualification to Proposal
Flow runs when configured to trigger on the transition
Opportunity description changes while already in Proposal
Depends on the selected update behavior
Opportunity changes from Proposal to Closed Won
Entry criteria for Proposal are no longer satisfied
Testing these scenarios helps identify repeated actions, missed triggers, and incorrect condition logic before the Flow is used in production.
Final Thoughts
Salesforce Flow entry criteria are an important part of building reliable CRM automation. They help administrators and developers control when record-triggered Flows run and reduce unnecessary processing.
Start with clear business requirements, select the appropriate AND or OR logic, and understand how update-trigger behavior affects existing records. For complex requirements, use custom condition logic or formulas carefully.
Most importantly, test both successful and unsuccessful scenarios before activating a Flow in production.
For businesses looking to improve their Salesforce automation, configuration, and CRM workflows, iBirds Software Services can help identify practical solutions that support their operational needs.
Top comments (0)