Conditional Logic
The test standing between a CRM rule firing and one of its actions running. Eight comparisons, written the way a document database writes them, and combined exactly one way.
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, each prefixed with a dollar
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.
Two levels, examining different material
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 payload by dotted path.
An unrecognised comparison passes
The evaluation is a switch with no fallback branch, 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 webhooks that act without being asked.
Thirteen node kinds on a canvas: send, wait, branch on behaviour, split, call task, tag, goal. Publish a version and in-flight leads keep their own place.
A unique URL per integration with HMAC signing, rate limits, payload caps and idempotency - plus a log of every delivery it ever accepted or refused.
Enrol a lead once and the sequence carries them: sends, waits, branches and exits, with a ledger that makes a duplicate send structurally impossible.
Weighted splits assigned by a deterministic hash of the enrolment, so a lead always takes the same arm no matter how often that step is run again.
Hold a lead for minutes or days between steps, clamped to the sending window you set, so that an overnight wait never lands at four in the morning.
Set the hours a sequence may send inside, as a fixed offset you enter yourself, and every wait is pushed forward into them before it is stored.
One do-not-contact roll per workspace, checked when a lead is enrolled and again inside the send, straight after that send has taken its own claim.
New leads enrol themselves the moment they are created, and the four guards that can refuse an add are read on every single route into a cadence.
Drop a call step into a sequence and it raises an assigned task on the lead's owner, with the outcome the rep logs coming back as a branchable answer.
Name a linked deal as the outcome that means the sequence worked. Reaching it stamps goal met on the run and takes the branch you wired behind it.
Twenty-six behaviours attach to wrap-up codes, and twenty codes ship already pointing at one, so ending a call the right way books the follow-up.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
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