Conditional Node
Branch workflow logic based on conditions.
The Conditional node is a planned logic node for branching workflow execution based on upstream values. It is designed to route the flow down one path or another so downstream nodes only run when their condition is met.
Intended purpose
Conditional is meant to branch workflow logic based on upstream values. Instead of every connected node always running, a Conditional node would evaluate a condition against its inputs and decide which downstream branch continues. It belongs to the logic and control group of nodes, alongside Merge, Delay, and Loop.
How execution works today
Understanding the current execution model explains why branching is a distinct capability. When you run a workflow, Builder Studio builds a plan from the connected graph and runs it as a directed acyclic graph: the planner orders nodes by their dependencies and the runner executes each node once its inputs are ready. There is no built-in branch primitive in that model. Every node that is reachable from the run target executes; the graph does not currently skip a node based on a runtime condition.
A Conditional node would add that missing primitive by letting a node gate which downstream nodes run, rather than relying on the static graph shape alone.
Related pages
- Merge node — combine multiple upstream branches back into one flow.
- Loop node — repeat a sub-flow over a collection.
- Workflows overview — how Builder Studio plans and runs a connected graph.
- Node types — the full node catalog.
Was this page helpful?