For Loop Connector

What this connector is for

Repeats a sequence of nested steps, either once per item in an array (For Each) or while a condition stays true (Do While). To stop a loop early from inside its own body, see Break Loop; to skip an iteration based on a condition without stopping the loop, wrap the relevant nested steps in a Conditional Branch instead.

All fields are listed in the action reference.

Inside the loop body, the current item and index are available two ways: as bare template variables using the names you chose ({{item}}, {{index}}), and via this step's own reference ({{<stepReference>.item}}, or under the uniform envelope {{<stepReference>.response.data.item}}). Both work identically; bare access is simpler unless an outer loop uses the same variable name.

For Each

Iterates over an array, running the nested steps once per item. The array can be a {{...}} expression or a JSON array string, which is parsed automatically. The index is 0-based.

• Record Identity gives each iteration a stable business key (e.g. {{item.sku}}) for cross-run history, per-record filtering and record-scoped rerun in batch jobs; it falls back to the iteration index.
• Progress: with exactly one loop anywhere in the call graph (including loops inside called workflows/routes), it is picked automatically as the batch job's primary progress source. With more than one, exactly one must set Primary Progress Source, otherwise the job's top-level progress follows whichever loop reports first.

Reading the response

• {{<stepReference>.response.data.iterations}} — items actually processed.
• {{<stepReference>.response.data.items}} — the original array.
• {{<stepReference>.response.data.results}} — each iteration's last-step output, in order.
• {{<stepReference>.response.data.failedIterations}} — nonzero only when a batch job's Continue On Iteration Error behavior kept the loop running past a failed item.
• {{<stepReference>.response.data.stoppedEarly}} — true if the loop stopped before consuming the whole array (execution deadline reached, or a Break Loop fired); remainingCount is how many items were never reached.
• {{<stepReference>.response.data.brokenEarly}} — true specifically when Break Loop stopped it, as opposed to the deadline.

Example

A loop named "For Each Line Item" (reference forEachLineItem) with Array Source {{trigger.body.lineItems}}: inside its body, {{item.sku}} and {{forEachLineItem.item.sku}} both read the current line item's sku; after the loop, {{forEachLineItem.response.data.iterations}} is how many ran.

Do While

Runs the loop body first, then repeats it while the Continue Condition stays true; no array is needed, so there is an index variable but no item variable.

• The condition is evaluated after each iteration, so the body always runs at least once. It uses the same condition shape as Conditional Branch (single comparison or nested AND/OR groups) and is commonly a {{runtimeVariables.x}} value set by a step earlier in the loop body (see Variable).
• Leaving the condition unset evaluates to false, so an unconfigured loop safely runs exactly one iteration.
• Max Iterations (default 1000, range 1 to 100000) is a hard cap so a condition that never turns false can't run forever.

Reading the response

• {{<stepReference>.response.data.iterations}}, .results and .failedIterations behave as in For Each.
• {{<stepReference>.response.data.reason}} — why the loop stopped: "condition_false", "break", "max_iterations" or "deadline".
• {{<stepReference>.response.data.stoppedEarly}} — true only when truncated by Max Iterations or the execution deadline. A false condition or a Break Loop are intentional, successful terminations, not "stopped early".
• {{<stepReference>.response.data.brokenEarly}} — true when reason is "break".

Example

Poll a job until it finishes, giving up after 50 attempts:

Continue Condition: {{runtimeVariables.jobStatus}} equals "pending"
Max Iterations: 50
Index Variable Name: attempt