Skip to main content

Loop Node

Iterate over arrays or repeat operations N times.

The Loop node is a planned logic node for repeating a sub-flow over a collection or a fixed number of times. It is designed to iterate part of a workflow so the same steps run once per item.

Not yet available
The Loop node is part of the planned logic-node set. It appears in the node reference catalog with its intended purpose, but it is not wired into Builder Studio execution yet. There is no Loop node type, canvas node, executor, or schema definition in the current product, so it cannot be added to a canvas or run today. This page documents the intended behavior so the contract is clear before the node ships.

Intended purpose

Loop is meant to iterate over arrays or repeat operations a set number of times. It would take a collection or a repeat count and run a connected sub-flow once per item, collecting the per-iteration results. It belongs to the logic and control group, alongside Conditional, Merge, and Delay.

Why iteration is a distinct capability

Builder Studio runs a workflow as a directed acyclic graph: the planner orders nodes by their dependencies and the runner executes each reachable node once. Because the graph is acyclic, there is no way to express repetition with edges alone — a node cannot feed back into an earlier node to run again. A Loop node would add controlled repetition on top of the acyclic model, running its inner sub-flow multiple times without introducing a cycle into the underlying plan.

What to use instead for now
Until the Loop node ships, there is no canvas primitive for iterating a sub-flow. For a known, small number of variations, duplicate the relevant nodes so each variation is its own static path in the graph.

Related pages

Was this page helpful?