new
All Plans
Automations & Integrations
Automations: Conditional Logic

Automations pick up a new Conditional Logic action that lets a single automation take different paths depending on record data. Solution Managers build conditions with the standard condition builder, then place the actions that should run when conditions are met and the actions that should run when they aren't. Route ITSM tickets to the on-call team when priority is high, auto-approve purchase requests under a threshold and route larger ones for review, or send only backordered line items down a follow-up path inside a Repeating Action loop.
Key Highlights
- Single Automation, Multiple Paths: Replace the pattern of duplicated automations (one per scenario) with a single automation that branches based on record data. Fewer automations to maintain, fewer places where logic can drift out of sync.
- Standard Condition Builder: Conditions use the same control that already drives filters and automation conditions — AND/OR combinations, grouped condition sets, all field types supported. No new syntax to learn.
- Any Action Type in Either Branch: Both the "conditions met" and "conditions not met" branches accept any of SmartSuite's automation action types — updates, notifications, record creation, integrations, and more.
- Per-Item Evaluation Inside Repeating Actions: Placed inside a Repeating Action loop, Conditional Logic evaluates once per item in the loop, so a single run can send some items down one path and the rest down the other.
- Nesting Support: Pairs with this same release's Advanced Logic Nesting to allow branches inside branches, loops inside branches, branches inside loops, and loops inside loops (two levels deep).
- Full Traceability: Run History shows the evaluated values on the Conditional Logic step, so teams can debug why a given item took the path it did.
How It Works
- Open an automation and add an action. Choose Conditional Logic from the action picker.
- Build the conditions in the standard condition builder — combine multiple conditions with AND/OR, group as needed, reference any of the triggering record's fields.
- Add the actions that should run when the conditions are met to the first branch, and the actions that should run when they aren't to the second branch. Any action type is allowed in either branch.
- To evaluate per item inside a loop, place the Conditional Logic action inside a Repeating Action — each item in the loop is evaluated independently.
- Save and enable the automation. Open Run History to see which branch ran for each execution.
Solution Managers and Workspace Administrators can build and edit these automations. Available on all plans.