Use typed record tables to drive List Iterator workflows and compose reusable nested subflows.
Where: Flowgen → left rail → Add → Bring in → Items List; group nodes from the canvas right-click menu
Key ideas
- Nested groups: Groups expose typed sockets, can contain groups, and can be collapsed into a reusable subflow/mini app.
- Groups organize; List Iterator repeats: Plain Groups still provide nested structure, typed sockets, reusable components, mini apps, and publishing. Their former Group Repeater / loop mode is deprecated; use a paired source and Results List for repetition.
Steps
- Create an Items node and define its columns/rows.
- Connect the source Items List to the body and a Results List with List Iterator.
- Expose/bind per-item and shared sockets.
- Run the source List or the owning flow and inspect per-item results.
Items is a typed table
- Rows are loop iterations.
- Columns become named typed per-item channels.
- A one-column text table is the simple list case.
- Rows can be edited/reordered on the card and AI Fill can derive or size a set.
Group input semantics
- Per-item sockets receive the matching column value for each iteration.
- Shared sockets broadcast the same value into every iteration.
- Previous-results input lets later iterations use accumulated earlier outputs.
- Nested groups keep typed sockets so a larger workflow can be composed from smaller flows.
Tips
- For new repetition, use Repeat these items or create_list_iteration; never enable a loop/repeater mode on a Group.
- Start with two or three representative rows before filling a large batch.
- Keep shared references/models outside the per-item table unless they truly vary by row.
Troubleshooting
Every iteration receives the same value
Check that the socket is bound as per-item and mapped to the intended Items column rather than configured as shared.