Conditional Logic
Rules That Act Only When They Should.CRM workflow conditions that check each record before an action runs.
Add a condition to any workflow action and it runs only when the record passes. Compare a field to a value: equal, not equal, greater, less, or one of a list. Every condition must pass, so a rule acts on exactly the records you mean and leaves the rest alone.
- Eight comparisons
- A check on every action
- All must pass
How it works
- A rule firesA deal moved, a field changed
- The wide checkRight record type and field value?
- Each action’s own checkAmount over 10,000? Region one of a list?
- Fails a checkThat action is skippedPasses every checkThe action runs
Automation That Knows When to Leave a Record Alone.
Each action checks the record first, so a rule meant for big deals leaves small ones alone.
Give each action its own check, so one rule can treat different records differently.
Greater than and less than compare values as numbers, so 100 really is more than 99.
Match a field against one of a list, or none of a list, instead of building a rule per value.
Add a Condition in Three Steps.
Narrow the Trigger
On the rule, pick the record type, and optionally a field and the value it changed to.
Add a Check to an Action
Pick a field, a comparison and a value, like amount greater than 10,000.
Stack More Checks
Add as many as you need. The action runs only when every one passes.
How CRM Workflow Conditions Decide What Runs.
CRM workflow conditions are the checks between a rule firing and an action running. They are if/then rules for your CRM: if the record passes, the action runs; if not, it is skipped.
Adoptiv’s workflow condition operators cover eight comparisons: equal, not equal, greater than, greater than or equal, less than, less than or equal, one of a list, and none of a list. Greater than or less than compares values as numbers. A value with no comparison written around it is read as equal.
Conditions sit in two places. The trigger holds a wide check: the record type, and optionally one field that must have changed to a set value. Then each action can carry a finer check of its own, read against the same data. So one rule can act on part of what it matched and leave the rest.
All conditions are AND conditions: every one must pass. There are no OR conditions, no “not” and no grouping, so a rule meant for either of two cases is built as two rules. Text checks such as contains, begins with or is blank are not available. To pick a lead’s next step from what they did, use branch logic in a sequence instead.
Eight Comparisons, on Every Action.
Match a field to an exact value, or to anything but that value.
Compare numbers, with an or-equal version of each.
Match any value in a list you give.
Exclude every value in a list you give.
For Teams Whose Rules Have Exceptions.
Conditional Rules vs One Rule for Everything.
| What | Rules with no conditions | With Adoptiv |
|---|---|---|
| A rule for big deals only | Rules with no conditions: Fires on every deal | With Adoptiv: Checks the amount before acting |
| Several values to match | Rules with no conditions: A rule per value | With Adoptiv: One “one of a list” check |
| Different actions per record | Rules with no conditions: Separate rules to keep in sync | With Adoptiv: A check on each action, in one rule |
| Either of two cases (OR) | Rules with no conditions: Two rules | With Adoptiv: Also two rules: conditions are AND only |
Conditional Logic Questions, Answered.
What are workflow conditions?
Checks that decide whether a workflow action runs. If the record passes every check, the action runs; if not, it is skipped.
Which comparisons can I use?
Eight: equal, not equal, greater than, greater than or equal, less than, less than or equal, one of a list, and none of a list.
Can I use OR conditions?
Not within one rule. Every condition must pass. To act when either of two things is true, build two rules.
Can a condition check if a field contains a word or is blank?
No. Contains, begins with, is blank and between are not available. Use equal, one of a list or a number comparison instead.
Where do conditions go?
In two places: a wide check on the rule’s trigger, and a finer check on each action.
What are AND conditions?
Conditions that must all be true at once. In Adoptiv every condition on an action is an AND, so the action runs only when all of them pass.
Do greater than and less than work on text?
They convert both sides to numbers before comparing, so use them for amounts, counts and scores.
What is the difference between conditions and branch logic?
Conditions decide whether a CRM workflow action runs. Branch logic decides which path a lead takes in a sequence, based on what they did.
Can one rule do different things for different records?
Yes. Give each action its own condition. The rule runs the actions whose checks pass and skips the rest.
Still have a question? A real person replies in under 60 seconds in US business hours. Talk to our team →
14-day free trial
Build Rules That Act on the Right Records.
Add conditions to your first workflow in the free trial. Free for 14 days, no credit card.
14-day trial · no card · migration included