Text Batch → List

Text Batch → List is the mirror image of its sibling "Text List → Batch": it takes a batch of strings and hands you a LIST. That's it. The entire job is converting ComfyUI's batched STRING form back into a plain list-type output so the next node in line can iterate, index, or feed something that only speaks LIST.

It earns its place in exactly the same scenarios its sibling does, but headed the other way. A node upstream gives you a batch of prompts or labels; the node you actually want to use expects a LIST. Without a converter you'd be rebuilding that list by hand, one Text node per item - and you'd give up halfway and paste it as a literal instead.

How it works

As boring as it gets, and that's the compliment. It accepts a STRING batch input (marked as a list input), converts every element to a string, and outputs them as a text_list. Order is preserved, nothing is filtered, no whitespace is touched - unlike "Text Split → Batch", this node doesn't split or strip anything. It's a pure type conversion. The one defensive detail worth knowing: if something hands it a single non-list string, it wraps it in a one-element list rather than erroring, so a mis-wired graph degrades gracefully.

The input and output

• text_batch (required) - the batched STRING input.
• text_list (output) - the same strings as a LIST, in order.

Realistic use: run it right after a node that emits a batch of prompts and before anything that needs to plug a list into a per-item processor. Pair it with "Text List → Batch" or "Text Split → Batch" when you're shuttling text between nodes with different type expectations - the three of them are the text-adapter set for the pack.

Installing it

Same pack as everything else here:

cd ComfyUI/custom_nodes
git clone https://github.com/FugitiveExpert01/ComfyUI-FEnodes.git

Restart ComfyUI, find it under FEnodes (or install via ComfyUI Manager by searching "ComfyUI-FEnodes"). No extra dependencies.

Common issues

• The input refuses to connect. If the upstream node isn't outputting a list-type STRING, this node's input won't accept it - that's ComfyUI enforcing its type system, and the fix is to check what the upstream actually emits. A non-list input that somehow gets through is wrapped into a one-element list, so watch for "everything collapsed into one item" as the symptom.
• Items look different than expected. This node does no cleanup. If upstream strings had trailing spaces or odd characters, they arrive intact. Run a Text Split or trim node before this if you need clean values.
• Wrong direction again. Need list → batch, not batch → list? That's "Text List → Batch" - different node, same pack.