Loops and reusable project calls
Loops repeat a process for the items in a list. Use Loop Subflow to repeat a connected group of nodes. Use a project node's Loop Mode to run an existing workflow for several inputs.
Repeat steps for each list item
Connect the Loop branch to the work required for each item and the Done branch to the final output.

These branches serve different stages of the loop.
Set Loop Data to a list of items.

Supply an array rather than a single text value that only looks like a list. For example, ["first item", "second item"] is a JSON array with two items. The text first item, second item is one text value. Typing brackets into a text input alone does not guarantee that the result is an array.
Use a reference to a field that appears as a list in the upstream results. If the list is generated by a model, configure an array field with Structured outputs and templates. Run the upstream node, expand the field to confirm that it contains separate items, and use Map variables and expressions to select that field for Loop Data.
In the per-item step, insert Loop Subflow → current_item.

This reference supplies the item being processed during the current iteration.
Run the workflow and inspect the collected results.

Check that each input item has the expected corresponding result.
Call an existing workflow
In a project-calling node, select the workflow you want to reuse.

Start with Loop Mode set to No when passing a single input.
Map the selected workflow's required input to a live value from the calling workflow.

The value must match what the selected workflow expects to receive.
Run the caller and inspect the returned output structure.

Use the actual output fields when connecting the result to later nodes.
Call the workflow for a list
Set Loop Mode to Yes to pass a list of inputs.

Each item must satisfy the selected workflow's input requirements.
Run the list and inspect the collected responses.

Confirm that the returned results correspond to the supplied items before passing them onward.
Important behavior
The original project node processes list items one at a time. The Beta node can process independent items together.
If the repeated operation changes external records, each list item can cause a separate change.
Last updated
Was this helpful?

