CR Input Text List
Paste a stack of prompts, feed them one at a time
- TEXT_LIST_SIMPLE
The whole job, in one sentence
CR Input Text List takes a block of multiline text and turns it into a list of strings - one per line. That's the entire node. No models, no API keys, no hidden cost. You paste, it splits, something else iterates.
Why is that worth a page? Because batching is where ComfyUI workflows die. When you've got fifteen prompts to run through the same graph, the naive answer is to build fifteen copies of the graph and drag wires forever. The list-based approach is one graph and a list node, and this is the node that gets your raw text into the graph in the first place. It's the unglamorous glue of a very big pack.
Where it lives, and what the pack is
CR Animation Nodes is RockOfFire's kitchen-sink animation pack, distributed on GitHub and Civitai (the demo-workflow pack there dates to late 2023, when AnimateDiff workflows were the talk of r/comfyui). It ships a few hundred CR-prefixed nodes covering lists, text, audio, graphics, image, and scheduling. Most of that menu you'll never open. The list nodes - this one among them - are the part that quietly shows up in real workflows.
You'll find it under CR Animation/List in the node menu. Yes, there's a lot in that submenu. This one is the simple text-in, list-out one.
The one input and the one output that matter
text- a multiline string, empty by default. This is where you paste your batch: one prompt (or tag, or filename, or whatever) per line.TEXT_LIST_SIMPLE- the output, a list of plain strings.
That SIMPLE suffix is the thing to understand, because it's the difference between this node working and you staring at a red wire. This pack has two list flavors. TEXT_LIST carries [text, alias] pairs - the alias is a name for each entry, which the animation/scheduling nodes use to label or look up items. TEXT_LIST_SIMPLE is just the strings, no alias. This node produces the plain kind, and it will only plug into a socket typed TEXT_LIST_SIMPLE. If your downstream node asks for TEXT_LIST and you reach for this node out of habit, it won't connect - that's the pack's sibling CR Text List, not this one.
For plain "run this graph once per item" batching, this is the one you want. Paste, wire the list into an iteration or list-processing node in the same pack, done. In an animation context, that often means feeding per-shot prompts or camera notes into a schedule; in a stills context it's just prompt batching.
Install
The standard two ways, same as any custom node:
- ComfyUI Manager - search for
CR Animationand install CR_Animation_Nodes by RockOfFire, then restart ComfyUI. - Manual -
cd ComfyUI/custom_nodes && git clone https://github.com/RockOfFire/CR_Animation_Nodesthen restart.
No model files to download, no heavy Python deps for this node to worry about - it's pure string splitting. If Manager asks about installing a requirements file for the pack, let it.
Troubleshooting worth knowing
The type mismatch above is the #1 trip point, and it's the only one I'd pre-warn you about. One more thing to sanity-check rather than assume: how blank lines behave. If your paste ends with a trailing newline or has gaps between entries, the node's behavior toward empty lines determines whether you get empty strings in the list. Some downstream nodes tolerate those, some get confused - so if your batch comes out one item short or weird, clean the paste first before hunting deeper.
And if you loaded a workflow that's failing with a missing-node error and this node is in it: this is exactly the kind of pack that Manager's "Install Missing Nodes" button handles, because the whole CR family is one repo. That's the ComfyUI ecosystem in miniature - install the pack, restart, stop fighting it.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| TEXT_LIST_SIMPLE | TEXT_LIST_SIMPLE | — |