π CR Simple List
Type lines, get a ComfyUI list that fans out execution
- LIST
- show_help
CR Simple List is about as basic as a node gets, and that's exactly why it's useful: you type some lines of text, and it turns them into a ComfyUI list. Each line becomes one item, and because a list makes the graph execute once per item, that turns a single value input into "run this for each of these." It's the hand-built way to fan out a workflow across several prompts, filenames, seeds-as-text, or whatever you type.
Think of it as the manual counterpart to loading a list from a folder or a file - when you just want to jot down five things and iterate over them, this is the node.
How it works
You enter values in a multiline field, one per line. The node emits them as a list. That word carries all the weight in ComfyUI: a list is not one bundled value, it's a stream where each element triggers its own pass through the downstream nodes. So a CR Simple List of three lines feeding into a generation graph produces three runs. It's the mechanism behind batch-over-a-set-of-inputs without touching a batch tensor.
The inputs and outputs that matter
list_values(multiline STRING, default "text") - your items, one per line.
Outputs:
LIST- the items as a ComfyUI list (a wildcard type, so it adapts to what consumes it).show_help- the wiki-link string, ignore it.
Installing it
Ships in Comfyroll Studio (Suzie1 / RockOfFire), a large, long-running utility pack. Install via ComfyUI Manager (search "Comfyroll Studio," install, restart) or clone it:
cd ComfyUI/custom_nodes
git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git
then restart. No models, no dependencies.
Common issues
The concept that trips people is list-vs-batch. If a downstream node balks, or you expected one combined result and got several separate ones, remember this emits a list - the graph runs per item. To stack results back into a single batch (say, for a grid or a save-as-one), pass them through CR Batch Images From List or an equivalent.
Content-wise: each line is taken literally, so a trailing blank line becomes an empty item, and leading/trailing spaces ride along. Trim if it matters. And since the output is an untyped list, a downstream type error usually means the values don't match what the consumer expects (text where it wanted a number, for instance), not that the list itself is broken. If Comfyroll fails to load at startup with a traceback, reinstall the pack cleanly through Manager.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| list_values | STRING | text | β |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| LIST | * | β |
| show_help | STRING | β |