Text List

Text List does one simple thing: it bundles several separate text strings together into a single list output. Where Text String gives you one reusable value and Text Multiline gives you one block of multi-line text, Text List gives you several distinct entries as a collection - the right shape when a downstream node needs to iterate over multiple values rather than consume one.

Why the distinction matters

ComfyUI is picky about types, and "a list of strings" is a genuinely different shape from "one long string" even though both look like text. If you've got several prompt fragments, filenames, or labels you want treated as separate items - say, feeding into something that loops over each one, or into the suite's own Text Concatenate in its list-merging mode ("Merge lists of strings," distinct from the plain two-string Text Concatenate) - you need them arriving as an actual list, not as one string you'd have to split apart yourself downstream.

Where you'd use it

Anywhere you're assembling a small, fixed set of text values by hand and need them to travel together as discrete items - batch labels, a handful of style tags you want combined selectively later, or entries you're about to feed into list-aware operations elsewhere in the suite. It's a manual, hand-typed alternative to nodes like Load Text File, which reads a list of lines from disk instead - reach for Text List when you're defining a short set directly in the graph rather than maintaining it in an external file.

Installing it

Through ComfyUI Manager: search "WAS Node Suite", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui
cd was-node-suite-comfyui
pip install -r requirements.txt

Nothing extra to download - it's core text handling, no external dependency.

Troubleshooting

The main way this trips people up is exactly the type confusion described above: if a downstream node is complaining about receiving a list where it expected a single string (or vice versa), that mismatch is almost always at the boundary between Text List and whatever consumes it - check whether the receiving node actually wants a list-type input or a plain STRING before assuming either node is broken.

The suite-wide caveat still applies here too: WAS Node Suite has had no active development since the author stepped back in December 2023, so if this node - or the whole pack - vanishes from your menu after a ComfyUI update, that's typically a whole-suite import failure over a stale pinned dependency (BLIP support being the recurring culprit) rather than this specific node breaking. Check your startup console before digging further.