Condition Node

Control your workflow execution with conditional logic and branching paths.

Overview

The Condition Node allows you to create branching logic in your workflows. Based on the values from previous nodes or conversation responses, you can route users to different paths—enabling personalized and intelligent conversation flows.

How It Works

A Condition Node evaluates one or more conditions and routes the conversation based on whether the conditions are true or false.

Previous Node Output
Condition Node
True
Path A
False
Path B

Defining Conditions

Conditions are rules that evaluate data from your workflow. You can reference:

  • Fields from previous node responses
  • User message content
  • Form submission data
  • Tool outputs (e.g., classified intent)

Condition Structure

Field

The data field to evaluate

Operator

How to compare (equals, contains, etc.)

Value

The value to compare against

Supported Operators

equals

Exact match comparison

not equals

Value is different

greater than

Numeric comparison (>)

greater than equals

Numeric comparison (>=)

less than

Numeric comparison (<)

less than equals

Numeric comparison (<=)

modulus equals zero

Value is divisible (remainder is 0)

modulus not equals zero

Value is not divisible (remainder is not 0)

Combining Conditions

You can add multiple conditions and combine them using logical operators:

AND

All conditions must be true for the overall result to be true.

intent = "sales" AND urgency = "high"

OR

At least one condition must be true for the overall result to be true.

intent = "sales" OR intent = "support"

Example Use Cases

Intent-Based Routing

Route job applicants to an HR workflow and sales inquiries to a lead qualification flow.

IF intent = "Job Application Submission" → HR Flow
ELSE → Sales Flow

Urgency Escalation

Escalate high-priority issues to human agents while handling routine queries automatically.

IF urgency_level > 8 → Human Handoff
ELSE → Continue with Bot

Form Validation

Check if required information was provided before proceeding.

IF email is not empty AND phone is not empty → Process Request
ELSE → Ask for Missing Info

Best Practices

  • 1

    Keep conditions simple

    Complex nested conditions are hard to debug. Break them into multiple nodes if needed.

  • 2

    Always handle the false path

    Don't leave the false branch empty—provide a fallback experience.

  • 3

    Test edge cases

    Test with empty values, unexpected inputs, and boundary conditions.

Next Steps

Form Node

Collect structured data from users

Action Node

Trigger external actions based on conditions