flow_stage_list
Collect one value per stage into a list — the data side of the flow pipeline
- stage_info
- value_1
- list
- array
The flow collectors in this pack merge media - images, masks, latents, videos. flow_stage_list is the one that collects data. It's the "give me the thing from every stage as a list" node: each stage drops a value into its own input port, and after the last stage runs, you get one list holding all of them, in order. Same flow-stage mechanics as the video collectors, but aimed at prompts, seeds, numbers, and control values rather than pixels.
How it works
The node exposes a dynamic value_1, value_2, … input - one per stage, matched to the current stage_index (the node looks up value_{stage_index + 1}). On each stage it saves that value to a per-run batch directory on disk and returns an ExecutionBlocker, so stages 1..N-1 are no-ops from your graph's point of view. On the final stage it loads everything back and returns the full list. Two things make it robust rather than clever-for-its-own-sake:
- It records the type of the first stage's value (
multi_type.json) and refuses mismatched types in later stages with a clearTypeError- no more silently getting a list of mixed garbage. - It uses
IS_CHANGEDreturningNaN, the "always rerun" idiom, so it can't accidentally cache a stale stage.
Inputs and outputs
Inputs: stage_info (required - from flow_stage_begin), plus the dynamic value_1…N ports. Outputs: list - a true ComfyUI list (marked is_list, meaning it can fan out to many consumers or feed a node expecting multiple items) - and array, the pack's single-wire LIST container holding the same items. Yes, both: it hands you the same data in both shapes so you don't need a type-conversion node downstream.
Where you'd use it
The natural pairing is with the staged H3 samplers. Wire each stage's text output into its value_N port, and at the end you have every resolved prompt in one list - great for a summary or a save step. Same for collecting per-stage seeds or control parameters. If what you're gathering is actually video/audio/image data, use flow_stage_collect_multi instead - this node is for values, not media.
Install and gotchas
Install with the pack: ComfyUI Manager → "ComfyUI-Apt_Preset", or git clone https://github.com/cardenluo/ComfyUI-Apt_Preset into custom_nodes + install.bat, then restart. No models. The one thing that bites people: the type check is strict, so an empty string vs. a number across stages will trip the TypeError. Keep each stage feeding the same kind of value, and remember the value must be connected - leaving a stage's port empty raises "value_N is not connected," not a silent gap.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| stage_info | FLOW_STAGE_INFO | — | |
| value_1opt | * | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| list | * | — |
| array | LIST | — |