Loop
Turn a list into an ordered set of results with one reusable internal workflow.
Creators building and publishing workflows.
Apply the same transformation to every item in a list and return one ordered result.
Overview#
Loop takes an array, runs its internal workflow once for each entry, and returns the collected results in the original order.
Use it for jobs such as summarizing every review, enriching every lead, drafting one caption per product, or cleaning every row in imported data.
Loop
Ports#
- Input: Array (
array): Must be a real array from an upstream block. - Output: Collected Results (
result): One result per item in original order.
The outer Loop intentionally has only these two connections. The repeated work belongs inside the Loop editor, so the main workflow stays readable.
Build a useful loop#
- Connect a block that produces an array to Array.
- Select Edit loop workflow on the Loop card, or Open loop editor in the Inspector.
- Build the repeated transformation with the same Block Library, canvas, connections, and Inspector used by Workflow Studio.
- Choose the block whose value should be collected. When the body has one clear final block, Edgaze selects it automatically.
- Select Save loop. The Loop card shows the real internal graph as a read-only preview.
- Connect Results to the next block or directly to Workflow Output.
The current item enters the first internal block automatically. Internal blocks cannot be dragged onto the outer canvas, and outer blocks cannot accidentally become part of the Loop.
Control cost and failure size#
Max Iterations is the largest list the Loop will accept. Set it close to the outcome you promise. A three-block body with a limit of 20 can execute those body blocks up to 20 times, so large limits can multiply latency and provider cost.
Start with three representative items. Confirm that the result order matches the input order, then test an empty array and the largest list you intend to support.
If an internal block fails, treat the Loop as failed rather than assuming a partial result is complete. Keep the body focused so the failing item and block are easy to identify.
What the card preview means#
The preview uses the same node and edge rendering as workflow cards elsewhere in Edgaze. It is visual context, not a second editable canvas. Open the Loop editor to move, connect, configure, or remove internal blocks.
The preview is derived from the Loop body while the canvas renders. It is not copied into the saved workflow, so a larger internal graph does not create a second persisted graph payload.
Before you publish#
- The input is an array, not JSON text that still needs parsing.
- The selected result block represents the outcome buyers expect.
- The maximum iteration count matches the product promise and price.
- Empty input returns an empty result without unnecessary model calls.
- A short test preserves result order.
Related#
Was this useful?
Your response helps us improve the documentation.