Decisions condition

Condition

Evaluates dot-path clauses against memory/input and routes to a matching branch.

What does it do?

A crossroads. Decides which path the flow should follow based on a rule you define.

How does it work?

Evaluates logical rules (e.g. "Is the amount greater than $50?" or "Did the customer ask to talk to support?"). If the answer is YES, it goes one branch (true); if NO, it goes the other (false).

Why use it?

To create personalized experiences. For example: if the customer is already registered, offer them a VIP discount; if they're new, ask for their email.

Inputs

name	type
`text`	string

Outputs

name	type
`branch`	string
`matched_clause_index`	number

Branches

Dynamic branches derived from the configured clauses.

Configuration

clauses array<object> required

default_branch string required

Default configuration

{
  "clauses": [
    {
      "left": "text",
      "op": "exists",
      "branch": "matched"
    }
  ],
  "default_branch": "default"
}

Emitted events

This node does not publish events on the pubsub channel.