Conditions: the flow follows the matching branch

The block holds a list of rules, and you decide how they work together. In "first match" mode the bot checks the rules in order and takes the customer down the first one that fits — each rule has its own branch. In "all conditions" mode every rule must hold at once: then the customer follows the "yes" branch, otherwise "no". The customer never sees the check and gets the message on the branch they were sent to.

Mode

How the rules work together. "First match" — the bot takes the first rule that fits and follows its branch, and if none fit, it takes the "else" branch. "All conditions" — every rule must match at once: then the "yes" output, otherwise "no".

Conditions (rule list)

Each row is one rule. A row has a short name (id) that wires its branch to the next step on the canvas — for example tariff_pro. A row with no name won't be saved.

Comparison and values

In each rule you pick a comparison (the same twelve options as in "Branch": equals, contains, greater than and so on) and enter what to check against what. On the left and right you can insert variables, for example {{contact.vars.tariff}}. The "is empty"/"is not empty" rules need no right-hand value.

Add / remove condition

"Add condition" appends a new row, the trash icon removes an extra one. You can set up as many rules as you need branches.

"First match" mode, three rules: {{contact.vars.tariff}} equals "start", "business" and "pro" — each with its own branch and message. A customer with no plan matches none of the rules and takes the "else" branch — say, an invitation to pick a plan.