Conditional Logic
The check standing between a CRM rule firing and one of its actions actually running. Eight comparisons, and every one of them is an AND, so a rule that has to cover either of two things gets built twice.
Eight comparisons, and one way to combine them
configuration only- entity.status$eqqualifiedand
- changes.amount$gte25000and
- entity.owner_id$in[ortiz, bhatt]and
- entity.source$neimport
- contains
- begins with
- is blank
- between
- matches a pattern
Product figures from the platform’s own defaults - not customer averages
How it works.
Eight comparisons, and that is the whole list
Equal, not equal, greater, greater or equal, less, less or equal, one of a list, none of a list. A bare value with no comparison written around it is read as equal. The four ordering ones convert both sides to numbers before comparing.
Everything is an AND and there is no way to say otherwise
Tests are the keys of a single object and every one must hold. There is no OR, no negation and no nesting, so a rule meaning either of two things has to be built twice as two rules.
One wide check on the rule, a finer one on each action
The rule itself holds a wide sieve over what arrived: a record kind, and optionally one field that must have moved to a stated value. Each action then carries a finer test of its own, reading the same delivered data by name.
A typo widens the rule instead of breaking it
Nothing catches a comparison the evaluator does not recognize, so a key that is not one of the eight is skipped and the test it belonged to counts as satisfied. A typo widens the rule rather than breaking it.
One moment in every run.
Every run passes through the same seven. Conditional Logic is the lit one, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
8 facts- Comparisons
- Equal, not equal, greater, greater or equal, less, less or equal, one of a list, none of a list
- Not available
- Contains, begins with, is blank, between, and anything matching text by pattern
- Combining
- An implicit AND across every test. No OR, no negation, no grouping
- An unknown comparison
- Skipped without complaint. The test around it is treated as having passed
- Levels
- One wide sieve on the rule, one finer test per action. Stored apart and evaluated apart
- Where values come from
- The payload handed to the rule: record kind, identifier, changed fields and any data alongside, walked one dotted segment at a time
- When it runs
- Between the event arriving and each action being dispatched, so a rule can fire on some of what it matched and not the rest
- Not the same as
- This gates a CRM rule's action. Deciding somebody's next step from what they did is Branch Logic
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and outside triggers that act without being asked.
What you draw is the thing that runs, not a picture somebody then has to build. Thirteen kinds of step, and publishing never moves a lead off their own place.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
Enroll a lead once and the cadence carries them at their own pace. Nobody loses their place when the platform updates, and nobody is sent one message twice.
Two versions of one cadence, side by side. Nobody lands on both and nobody switches halfway, because the side is decided by arithmetic on their own record.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
One do-not-contact list per workspace, read on enrollment and read again inside the send, so an address added mid-cadence still stops the next message.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever they log at hang-up decides where that lead goes next.
Stop writing to somebody who already bought. Name the deal state that means the cadence worked, and reaching it stamps the run and takes the branch behind it.
The do-not-call mark, the callback and the task happen because a rep picked the code, not because they remembered. Twenty-six behaviors, twenty codes shipped.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See conditional logic on your own floor.
Thirty minutes, your numbers and your data. We will set conditional logic up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included