Conditions and comparison operators

Operators depend on the property type

A text property should not be compared in exactly the same way as a date or number.

Kanopee uses HubSpot property metadata to offer operator groups appropriate to the field. Supported groups currently include text, choice/owner/pipeline, multi-choice, boolean, number and date/datetime properties.

If an operator seems inappropriate or a property is missing, refresh HubSpot metadata before rebuilding the condition.

Text and choice comparisons

For text-like properties, available comparisons include:

• equals / does not equal
• contains any of
• contains all of
• does not contain any of
• starts with
• ends with
• is known; and
• is unknown.

Single-choice, owner and pipeline-style properties support comparisons such as is any of, is none of, equality/inequality and known/unknown checks.

Multi-choice properties also support contains-any, contains-all and contains-none style logic.

Number and boolean comparisons

Number properties can use comparisons including:

• equals / does not equal
• greater than / greater than or equal to
• less than / less than or equal to
• between; and
• not between.

Boolean properties support is true, is false, is known and is unknown.

Date and datetime comparisons

Supported date/datetime comparisons include:

• is on
• is before
• is after
• is between
• is not between
• is more than X days ago
• is less than X days ago
• is known; and
• is unknown.

Use the company/workflow time context carefully when the outcome depends on a specific date or time.

Combine conditions with AND or OR

Kanopee's condition groups can be configured as:

• All criteria must match (AND); or
• Any criterion can match (OR).

In an If/then branch, each branch has its own condition group. Branches are evaluated in order, and the first matching branch is followed.

The current editor focuses on flat condition rows; more complex nested condition structures are not fully exposed in the UI.

---