Router Node Parameters

The Router node (action_router) performs conditional branching by rules. Depending on context (channel, ticket status, tags, priority, etc.) execution goes to one of the branches. In Node Inspector (right panel) the following sections are available:

Mode

• first_match — the first branch whose conditions are met is executed.
• all_matches — all branches whose conditions are met are executed (parallel execution).

Rules

• branch_id — branch identifier that connects to the edge (arrow) on the canvas. Each rule leads to a separate branch.
• conditions — array of conditions (field, operator, value, nextLogic, groupStart, groupEnd).
• logic — logic between conditions (AND, OR).

Default Branch (default_branch)

• Else — branch executed when no rules match.
• On the canvas it connects to the "Else" edge or similar.

Tip: branch_id — connects to button/edge; default_branch — when no rules match.

Rule Structure

Each rule contains:

Available Context Fields (field)

Field in the Node Inspector is a closed list. You do not enter arbitrary scenario variables (user_choice, etc.) here. To branch on a scenario constant, see Action switch in Built-in actions.

• channel — channel (telegram, viber, whatsapp, widget, facebook, etc.).
• request_type — request type.
• status_name — ticket status name.
• priority — ticket priority.
• subject — request subject.
• request_tag — request tag.
• client_tag — client tag.

Operators

• equals — equals.
• not_equals — not equals.
• in_list — value is in list.
• empty — field is empty.
• not_empty — field is not empty.

Logic (nextLogic)

• AND — all conditions in the group must be met.
• OR — at least one condition must be met.

Related Documents

• Create scenario
• Use action in scenario
• Scenario editor overview