Kantos

Conditions let you filter when automations should run. Define rules using field operators and combine them with AND/OR logic for precise targeting.

Condition Structure

{
  "conditions": {
    "match": "all",
    "rules": [
      {
        "field": "status",
        "operator": "equals",
        "value": "new"
      },
      {
        "field": "lead_source",
        "operator": "is_not_empty"
      },
      {
        "field": "email",
        "operator": "contains",
        "value": "@"
      }
    ]
  }
}

Available Operators

Operator	Description
`equals`	Exact match
`not_equals`	Not an exact match
`contains`	Contains the value (text)
`not_contains`	Does not contain the value
`starts_with`	Starts with the value
`ends_with`	Ends with the value
`is_empty`	Field has no value
`is_not_empty`	Field has a value
`greater_than`	Greater than (numbers/dates)
`less_than`	Less than (numbers/dates)
`in`	Value is in a list
`not_in`	Value is not in a list

AND vs OR Logic

Use "match": "all" for AND logic (every condition must be true), or "match": "any" for OR logic (at least one condition must be true).

Combining Logic

For complex scenarios, use nested condition groups. For example, match ALL of: status is "new" AND (source is "website" OR source is "referral").

AND Example

{
  "match": "all",
  "rules": [
    { "field": "status", "operator": "equals", "value": "new" },
    { "field": "estimated_value", "operator": "greater_than", "value": 5000 }
  ]
}

Both conditions must be true: the record must be new AND have a value over 5000.

OR Example

{
  "match": "any",
  "rules": [
    { "field": "source", "operator": "equals", "value": "website" },
    { "field": "source", "operator": "equals", "value": "referral" },
    { "field": "source", "operator": "equals", "value": "event" }
  ]
}

At least one condition must be true: the source is website, referral, or event.

Next Steps

Triggers — Events that start your automations
Actions — What happens when conditions pass
Automations Overview — Full automation guide