Filters and conditions are the core of every query. This article shows the full toolkit and the common patterns you'll keep coming back to.
Anatomy of a Filter
- Field: Any field on the source datastore, including custom fields and fields on linked records.
- Operator: Adapted to the field type — date fields get date-specific operators, dropdown fields get is-in/is-not-in.
- Value: Literal text/number/date, a variable (current_user, today), or another field reference.
- Connector: AND or OR with the next condition in the group.
Operators by Field Type
- Text: equals, not equals, contains, does not contain, starts with, ends with, matches regex.
- Number: equals, not equals, greater than, less than, between, is null.
- Date: equals, before, after, between, within (relative).
- Boolean: is true, is false.
- Dropdown/multi-select: is, is not, is in (list), is not in.
- Linked record: is, is not, related-record matches sub-condition.
Useful Variables
current_user— the running user.current_user.group— their primary security group.today,now,yesterday,tomorrow.this_week_start,this_month_start,this_quarter_start,this_year_start.days_ago(n),days_from_now(n).
Worked Examples
- My open tickets: assignee = current_user AND status = open.
- Recently created: created_at > days_ago(7).
- Stale items: last_activity < days_ago(30) AND status = active.
- Date range overlap: start_date ≤ today AND end_date ≥ today.
- Linked record condition: customer.country = UK AND total > 5000.