Collapse a connected region behind typed inputs and outputs, nest it inside larger workflows, or pair it with a List Iterator outside the Group.
Where: Select connected nodes → Group
Key ideas
- A group is a subflow: Grouping preserves the interior nodes/connections while presenting an authored public interface of typed inputs and outputs.
- Nesting is compositional: Groups can contain groups, so a larger workflow can be assembled from smaller independently testable stages.
- 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
- Select one coherent connected stage and create a Group.
- Expose only the inputs/outputs that callers need, name them by meaning, and assign matching types.
- Test the group once as a normal subflow before nesting it; use List Iterator outside the Group when rows must repeat.
- For repeated rows, connect a source Items List and Results List with List Iterator, wire Current <field> values to body inputs, then inspect the collected Results List.
Group boundaries
Expose the smallest stable contract. Internal prompts/models/helpers can change later without forcing every caller to rewire, as long as the public socket names and types remain compatible.
Tips
- For new repetition, use Repeat these items or create_list_iteration; never enable a loop/repeater mode on a Group.
Troubleshooting
A nested group cannot connect to its caller
Compare the exposed socket type with the caller handle, resync the group exposure, and avoid hiding an output that an outer flow still consumes.