The Condition node branches your workflow. It checks one or more conditions and routes execution down a true path or a false path, so different results can trigger different steps.
What it does
- Evaluates condition groups and sends the run down the true or false branch.
- Combines conditions inside a group with AND or OR.
- Compares text and numbers with a range of operators.
- Forwards the upstream content down whichever branch is taken.
How groups work
Each condition group has a type of AND or OR and a list of conditions. A condition compares an input value against a value you set using an operator. Inputs accept variable tags, so you can test the output of an earlier node.
Operators available: equals, contains, starts with, ends with, greater than, and less than.
Two handles
The node has a true handle and a false handle. Connect both in most workflows so every run has somewhere to go. The content coming into the node is forwarded down the branch that is taken.
Configuration reference
| Field | Required | What it does |
|---|---|---|
| Condition groups | Yes | One or more groups. Each group is AND or OR and holds conditions of input, comparison, and value. Inputs support variable tags. |
Local or Cloud, and cost
Condition runs in both Local and Cloud modes and costs 0 credits.
Worked example: route by sentiment
- Add an AI Sentiment Analysis node upstream.
- Add a Condition node with one AND group and one condition: input
[Input from sentimentAnalysis-1], comparison equals, valuepositive. - Wire the true handle to a thank-you email, and the false handle to a support task.
Related
Was this helpful?
Contact us