Loop component (AI Flowi Workflow)
Loop processes items individually and gathers the results. Place it between a source of tabular data and the steps you want to apply to each item.
Loop is documented in the catalogue; not production-tested by Ai Flowi. This reference describes the exported inputs and outputs for AI Flowi Workflow 1.9.2.
By Ai Flowi · Published
Inputs
| Name | Type | Required | Accepted input types | Plain explanation |
|---|---|---|---|---|
data | other | No | DataFrame, Table | The source to iterate over. Connect a DataFrame or Table output; these are the accepted connection types listed for this input. |
The description mentions Data or Message objects, but the exported data input lists only DataFrame and Table. Use the input types in the table when choosing an upstream connection; the description alone does not establish a Data or Message connection.
Outputs
| Name | Display name | Type | Purpose |
|---|---|---|---|
item | Item | JSON | The individual item for processing in the loop. |
done | Done | Table | The gathered loop results, exposed as a Table. |
When to use Loop
Use Loop when one collection needs item-by-item processing and gathered results. Its Item port exposes JSON, while Done exposes a Table; choose the downstream input to match the port you need. When the source has another type, inspect Type Convert, which lists a Table output, before configuring Loop.
Related: Batch inference: preserve row identity and reconcile partial results.
When to choose another component
For a single JSON object that needs fields changed, choose JSON Operations. For one message that needs a comparison and two routes, use If-Else. If the goal is to reuse a flow as a component, consider Sub Flow; reuse alone does not require item iteration.
Minimal configuration example
example configuration, not a recorded test
This is a wiring example, rather than a pasteable JSON value. It uses the sole input name exported for Loop.
data- Connect an upstream DataFrame or Table output.
Inspect Item for the per-item JSON and Done for the gathered Table. The export does not list a separate return input or a complete loop-back configuration, so this example does not invent one.
Limitations
- The data input is marked optional. That flag does not document what an empty or disconnected source returns.
- The catalogue gives no iteration limit, ordering rule, concurrency setting or retry policy for Loop. Check those behaviours in your configured flow before relying on them.
- No end-to-end loop test is recorded in the supplied live template pages. The wiring example establishes neither successful execution nor measured usage.
Related components
Sub Flow · JSON Operations · Type Convert · If-Else
Node usage
Plans: Go from USD8/month billed yearly (USD10 monthly), Plus from USD16 (USD20 monthly), Pro 100 from USD80 (USD100 monthly), Pro 200 from USD160 (USD200 monthly) and Pro 500 from USD400 (USD500 monthly), with 5,000 to 250,000 Flowi Tokens/month and top-ups; 1 token per node run; third-party API and model usage is not included.
Reference source
Component catalogue: flow_controls.LoopComponent, AI Flowi Workflow 1.9.2, exported 9 October 2026.