Text String

Text String is about as simple as ComfyUI nodes get: it holds a single line of text and outputs it as a STRING. No processing, no logic - just a value you type once and can wire to as many downstream nodes as you want.

Why bother with a dedicated node for this

ComfyUI's native STRING widgets are usually tied directly to whatever node they live on - if three different nodes need the same filename prefix or the same short label, you're typing it three times and hoping you don't typo one of them. Text String gives you a standalone value with its own output socket, so you set it once and route it wherever it's needed: into a filename, into Text Add Tokens as a value to substitute, into a Text Concatenate chain, or into anything else expecting a STRING. It's a small thing, but it's the difference between "one source of truth" and "three copies that can drift out of sync."

How it compares to its siblings

The suite has a few text-input flavors and it's worth knowing which is which. Text String is a single line. Text Multiline is the same idea but for paragraph-length text - full prompts, notes, anything spanning more than one line. Text List is different again: it holds multiple separate string entries as a list, for nodes further downstream that iterate over several values rather than consuming one. If you just need one short reusable value, this is the lightest option of the three.

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 needed for this node specifically - no models, no special dependencies.

Troubleshooting

There's genuinely very little to break here - it's a static value. The one thing to watch for is accidentally leaving trailing whitespace or a stray newline in the field if you copy-pasted the text in; that can produce confusing mismatches downstream in nodes doing exact string comparisons, like Text Compare or Text Find.

The suite-wide caveat still applies even to a node this simple: WAS Node Suite hasn't been actively developed since December 2023, so if it's missing from your node menu entirely after a ComfyUI update, that's a whole-pack import failure (usually a pinned legacy dependency like BLIP support conflicting with the newer core) rather than anything wrong with this specific node. Check your startup console before assuming Text String itself is the problem.