Roboteka
Roboteka · Robots · Compound condition (AND / OR / NOT)

Compound condition (AND / OR / NOT)

The Compound Condition robot evaluates several conditions with AND, OR and NOT grouping in Bitrix24 (Alaio) business processes and robots. It accepts up to four value pairs with comparison operators (eq, neq, gt, lt, contains, is_empty and more) or a JSON tree of arbitrary nesting, and returns a single Y/N flag for conditional branching.

The robot combines several checks into a single condition, replacing chains of nested Condition blocks in the workflow designer. Flat mode takes up to four value A — operator — value B pairs and AND or OR combining logic; JSON mode supports arbitrary nesting of and, or and not groups. Operators: eq, neq, gt, lt, gte, lte, contains, not_contains, starts_with, ends_with, is_empty, not_empty, matches; string comparison is case-insensitive by default. Typical use cases: before a deal stage change, verify the amount exceeds a threshold and the contact phone is filled; route a lead down the right branch when the source is advertising or the website. It returns a Y/N flag — compare it in the condition of the next step of the business process.

What input parameters does the robot accept?

Parameter Type Required? Default
Conditions as JSON (takes priority over flat mode). Format: {"and":[{"a":"X","op":"==","b":"Y"},{"or":[...]}]} string —
Combining logic: AND (all must be true) / OR (at least one) string —
Condition 1 — value A string —
Condition 1 — operator (==, !=, <, >, contains, is_empty …) string —
Condition 1 — value B string —
Condition 2 — value A string —
Condition 2 — operator string —
Condition 2 — value B string —
Condition 3 — value A string —
Condition 3 — operator string —
Condition 3 — value B string —
Condition 4 — value A string —
Condition 4 — operator string —
Condition 4 — value B string —

What does the robot return?

Parameter Type
Result (Y/N) string

What errors can the robot return?

The robot writes these messages to the business process log when it cannot complete a step. The text tells you what to fix in the settings or the data.

  • Error: invalid JSON in conditions_json
  • Error: no conditions defined

Scenario: deal check before a stage change

  1. A deal enters the Approval stage
  2. The robot checks that the amount is over 100000 AND the source equals Website
  3. On Y the process moves the deal forward, on N it returns the deal to the manager

Related robots

Related articles

Install Describe a task — we build the robot for free