Field and rule types reference

Every field type, what it accepts, and the values that surprise people.

Field types

The same types are used for what you store about your own records and for what the bot asks a lead.

Type	Accepts	Notes
`TEXT`	A single line	Optional maximum length
`TEXTAREA`	Several lines	Optional maximum length
`NUMBER`	Any number	Optional minimum and maximum
`CURRENCY`	A whole number of cents	See below
`EMAIL`	A valid email address	Format is enforced
`PHONE`	A phone number	Optional format pattern
`URL_LIST`	A list of valid URLs	Each one is checked
`SELECT`	One option from a category group	The option must be active
`MULTI_SELECT`	Several options from a category group	Every one must be active

Currency is stored in cents

Whole cents, always, with no fractional part. 50,000 is stored as 5000000.

The dashboard converts for you: you type what you mean and read what you meant. The storage format only becomes visible in two places, and both catch people out —

Qualification rule values, which you type in the stored form. A minimum budget of 50,000 is a MIN_VALUE of 5000000.
Imports and API calls, where nothing converts for you.

Integers rather than decimals is deliberate: a price that is the sum of three numbers should not depend on how a floating-point number rounded.

Choice fields and category groups

SELECT and MULTI_SELECT read from a category group — a named list managed at Configuration → Categories.

An option must be active to be chosen. Deactivating one stops it being offered without rewriting the history of everything already tagged with it.
One group can serve both sides. That is what makes CATEGORY_OVERLAP matching work: the lead's answer and your record's tags come from the same vocabulary, so overlap means something.

Rule types

Type	Applies to	The value you give
`REQUIRED`	Any field	—
`MIN_VALUE`	`NUMBER`, `CURRENCY`	The floor
`MAX_VALUE`	`NUMBER`, `CURRENCY`	The ceiling
`MIN_LENGTH`	Text fields	A character count
`REGEX`	Text fields	A regular expression
`IN_LIST`	Choice and text fields	The allowed values

Two behaviours are worth stating plainly:

Only REQUIRED cares about an empty answer. Every other rule passes when the field is blank, because there is nothing to judge. If an answer must exist and be within a range, that is two rules.
IN_LIST on a multi-select requires every chosen value to be allowed, not just one.

Match types

Type	Compares	Can be a hard filter
`EXACT`	Two values, ignoring case and spacing	Yes
`CONTAINS`	Text within text	Yes
`RANGE`	Two numbers, with fall-off	Yes, with tolerance
`CATEGORY_OVERLAP`	Two tag lists	Yes, with a threshold
`CUSTOM_LLM`	Anything, judged by the model	No

A missing value on either side scores 0.5 and never fails a hard filter. Full explanation in Matching dimensions and weights.

Was this helpful?