Loop Over Items

Run downstream nodes once for each input item, then continue on Done

Usage and specifics

Use this node to run an action per item or batch. Loop carries repeated processing; Done continues once all items are processed.

With this manual payload:

{
  "contacts": [
    { "email": "[email protected]" },
    { "email": "[email protected]" }
  ]
}

1. Set Items to iterate (source) to input.contacts and Items per iteration to 1.
2. Connect Loop to Edit fields, enable Mapped fields only and create email with {{ nodes.loop1.item.email }}. Replace loop1 with the technical name offered by your mapping.
3. Connect Done to processing that should happen after all contacts. You may connect the last body node back to the loop; the engine manages iteration.

During each turn, loop output supplies item, items, zero-based index, total and batchSize. Here, item is the Ada contact followed by the Lin contact. input.contacts stays the original list: it is not the current item.

On Done, output contains collected results in items and their number in count. With the preparation node above, expect:

{
  "items": [
    { "email": "[email protected]" },
    { "email": "[email protected]" }
  ],
  "count": 2
}

Results come from the output collected at the end of each turn, rather than automatically from the original items. With several items in a batch, item becomes a list; the last batch may contain only one item. If an action expects a single contact, keep batchSize: 1.

Technical type : loop_over_items. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Configuration help

source
Items to loop over

Connect the Loop output to the nodes to run for each item. Optionally connect the last node back to this node (like n8n). When finished, execution continues on Done with all iteration outputs.

batchSize
Items per iteration

Number of items processed per loop iteration (1 = one at a time).

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

{
  "source": "",
  "batchSize": 1
}

Verification

Run the complete workflow with both contacts and check that each appears once in the results. Then test an empty list: the body should not run and Done should remain reachable. Check the final output after the loop, where item is replaced by the result collection.

See also : Expressions and data, Executions, Node catalog.