Choose the right condition operator

Updated 19 October 2026 · For back office users

Each condition compares a field on the record with Value 1 (and Value2 for range) using an operator.

Operators

Operator	Matches when	Example Value 1
`equal`	The field equals Value 1. Capitals don't matter.	`Active`
`not_equal`	The field doesn't equal Value 1.	`Withdrawn`
`in`	The field equals any item in a comma-separated list. Spaces around items are ignored.	`ENG1, MAT2, SCI3`
`not_in`	The field equals none of the items in the list.	`13, 14`
`contains`	The field's text includes Value 1 anywhere. Capitals don't matter.	`@example.com`
`does_not_contain`	The field's text doesn't include Value 1. An empty field counts as not containing it.	`test`
`greater_than`	The field is more than Value 1, as a number or a date.	`1000`
`less_than`	The field is less than Value 1, as a number or a date.	`2026-09-01`
`range`	The field is between Value 1 and Value2, including both ends.	Value 1 `16`, Value2 `18`

Special values for equal, not_equal, in and not_in

Null matches an empty or blank field. Use equal with Null to find missing values, or not_equal with Null to find filled-in ones.
True and False match yes/no fields, whatever the capitals.

Numbers and dates

greater_than, less_than and range first try to compare as numbers, then as dates. If the values can't be read as either, the condition doesn't match.
Write dates as yyyy-MM-dd, such as 2026-09-01, to avoid any confusion between day and month.
range needs both values. If Value2 is empty, it never matches.

Comparing with another field

Put $$FieldName$$ in Value 1 or Value2 to use another field's value from the same record, for example greater_than $$TargetScore$$.

List fields from REST APIs

When the field is a [*] path, such as courses[*].code, the condition looks at every item. equal, in, contains and the number and date operators match when any item matches. not_equal, not_in and does_not_contain match only when no item matches. An empty list is treated as an empty field.