Text to String

If you've ever wired something into a WAS text node and gotten a type-mismatch error where you least expected one, Text to String is probably the fix. It's a small conversion node, and the reason it exists is a piece of pack history worth knowing: back in May 2023, WAS Node Suite deprecated its own ASCII output type in favor of plain ComfyUI STRING, specifically - per the changelog - "so that it is more clear what data is being passed." Text to String is the bridge for that transition: it takes text coming out of the suite's older or non-standard text handling and hands you back a normal STRING you can plug into anything.

Why this matters in practice

ComfyUI's type system is strict about sockets - a STRING output only connects to a STRING input, full stop. WAS Node Suite predates a lot of the ecosystem's conventions, and parts of its text pipeline (dictionary values, list items, legacy ASCII-mode output if you've still got use_legacy_ascii_text set) don't always arrive as a clean STRING by default. Rather than make every downstream node guess, the suite gives you this one explicit conversion step. Wire your text-ish value in, get a STRING out, connect it to CLIPTextEncode, Save Text File, Text Concatenate, or any other native or third-party node that wants a plain string.

Where it fits in a graph

Think of it as the universal adapter at the end of a WAS text chain. You'll typically see it right before a value leaves "WAS land" and enters the rest of your workflow - after a Text Dictionary Get, a Text Find and Replace pass, or anything that's been living inside this suite's text tooling. If a node several steps downstream complains about an unexpected type on what looks like plain text, this is the node to drop in between.

Installing it

It ships as part of the full suite - there's no separate install. Through ComfyUI Manager, search "WAS Node Suite" and install. 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

Restart ComfyUI afterward - like the rest of the suite, nodes register at startup.

Troubleshooting

The suite hasn't seen active development since the author stepped back in December 2023, so don't expect this node's behavior to change going forward - what you see is what you get, forever, unless you fork it yourself. The bigger practical risk is the suite failing to import at all after you update ComfyUI's core: WAS-NS pins some dependencies (its BLIP support is the usual trigger) that conflict with newer core requirements, and the fix community members land on most often is deleting and reinstalling the node's requirements inside your venv, or just uninstalling the offending legacy BLIP path if you don't need it.

If Text to String specifically is passing through something that still looks wrong downstream - extra whitespace, quote characters, or dictionary-style formatting - that's almost certainly baked into the upstream WAS text node you fed it, not this converter. Trace back one step and check what's actually leaving that node before assuming the conversion is at fault.