Automations
Conditions
Branching on contact fields, tags, timing and previous steps.
Conditions in two places
Trigger conditions
Checked before enrolment. A failed check means no run is created.
Continue-if step
Checked during a run. A failed check is logged as skipped and ends the run as completed.
Use trigger conditions when the workflow should never start for the wrong record. Use a continue-if step after earlier actions or a wait when the record should be checked again at that point in time.
Build a condition group
- Add a condition in the trigger card or choose the Only continue if action.
- Choose the subject, such as Contact status, Contact tag, or Trigger data.
- Select an operator and enter or choose the comparison value.
- For a continue-if step, choose whether all conditions or any condition must pass.
- Save and publish the workflow.
Condition subjects
Contact field
First name, last name, email, phone, business name, city, state, or country.
Contact tag
Whether the contact currently has the selected tag.
Contact status
The current CRM status, such as LEAD, ACTIVE, or CUSTOMER.
Lead source
The contact's current lead source text.
Custom field
A value from the contact's custom field object, addressed by its field key.
Pipeline stage
Reserved for opportunity context. Current workflow runs do not load a deal into this subject.
Deal value
Reserved for opportunity context. Current workflow runs do not load a deal into this subject.
Trigger data
A top-level field from the event payload, addressed by its exact key.
Current time
The UTC timestamp at the moment the condition is evaluated.
Operators and values
Is / is not
Case-insensitive text equality or inequality.
Contains / does not contain
Case-insensitive text inclusion. For tags, this checks membership.
Is set / is not set
Checks for a present, non-empty value and needs no comparison value.
Greater / less than
Converts both values to numbers before comparing them.
Before / after
Parses both values as dates and compares their timestamps.
Payment amounts and deal values are stored in the currency's smallest unit. For example, an amountCents trigger value of 12500 represents $125.00 for a two-decimal currency.
Missing data is a normal false result
A missing contact, unknown field key, invalid number, or invalid date does not crash the workflow. It evaluates false. The exceptions are is not anddoes not contain, which can be true for a present value that differs, and the explicit is not set check.