The Conditional Logic action lets a single automation take different paths depending on your data. Instead of building separate automations for each scenario, you add one Conditional Logic action, define the conditions to check, and place the actions that should run when those conditions are met — and the actions that should run when they aren't.
Plan Availability |
|
Permissions | Solution Managers and Administrators can create and edit automations. |
Related Reading | SmartSuite Automation Actions · Automation Conditions · Repeating Actions |
Overview
Conditional Logic evaluates record field values using the standard condition builder — the same control you already use for filters and automation conditions — and then branches:
Conditions met → runs the actions you place in the first branch.
Conditions not met → runs the actions you place in the second branch.
It can evaluate:
The triggering record — the record that started the automation.
Each item inside a Repeating Action loop — so every item in a loop is evaluated individually and takes its own path.
Adding a Conditional Logic Action
Open the automation you want to edit, or create a new one.
Click to add an action and choose Conditional Logic.
Build your conditions using the condition builder. Combine multiple conditions with AND / OR, and group conditions as needed — the same way you build filters elsewhere in SmartSuite.
Add actions to each branch:
Place the actions that should run when the conditions are met.
Note that there is no automated "not met" path - any paths that meet their criteria will run.
If multiple paths meet their criteria, all matching paths will run.
Save the automation and enable it when you're ready.
What You Can Put in a Branch
Each branch holds its own sequence of actions, and they run in order just like actions in the main automation flow. All automation action types are allowed within a branch.
Using Conditional Logic Inside a Repeating Action
When a Conditional Logic action sits inside a Repeating Action loop, the conditions are evaluated once per item in the loop. Each item independently follows the met or not-met branch, so a single run can send some items down one path and the rest down the other.
This is useful when a loop processes a mixed set of records — for example, iterating through line items and only creating a task for the ones over a certain amount.
Nesting Advanced Logic
You can nest Advanced Logic to build multi-level workflows. Supported combinations:
A branch inside a branch — check a further condition inside a branch you've already entered.
A loop inside a branch — run a Repeating Action only when conditions are met.
A branch inside a loop — evaluate conditions separately for each item in a loop.
A loop inside a loop — iterate through a nested set of items.
Two levels of nesting are supported. At the second level, Looping and Conditional Logic actions are not available.
Troubleshooting
The wrong branch ran. Open Run History and expand the Conditional Logic step to see the values that were evaluated.
Nothing ran in either branch. Check that the branch you expected has valid conditions, has actions in it, and that the automation is enabled.
Conditions reference a deleted field. A condition pointing at a removed field can't evaluate — update the condition to a valid field.
Practical Scenarios and Use Cases
1. Route Requests by Priority
Scenario: High-priority requests need to page the on-call team; everything else just needs a queue entry.
Solution: Add Conditional Logic on Priority is High — the met branch sends a Slack notification, the not-met branch creates a standard task.
2. Approve or Reject Based on Amount
Scenario: Purchases under a threshold can be auto-approved; larger ones need review.
Solution: Condition on Amount is less than 1,000 — met branch sets Status to Approved, not-met branch assigns a reviewer and notifies them.
3. Per-Item Handling in a Loop
Scenario: An order contains many line items, and only backordered ones need follow-up.
Solution: Inside a Repeating Action over the line items, add Conditional Logic on Stock Status is Backordered so only those items generate a follow-up task.