String to Text

WAS Node Suite's text ecosystem carries more history than most packs' do. The README itself flags one piece of it directly: ASCII used to be the standard type its text nodes output, and it's now deprecated in favor of STRING - the change was made, in the author's own words, "so that it is more clear what data is being passed." That kind of evolution is exactly why a bridge node like String to Text exists: a plain STRING, the type most of ComfyUI's own primitives and other packs use, isn't automatically the same thing as whatever internal text representation a given WAS node was built to expect. String to Text is the adapter that takes a STRING and converts it into WAS's text type, so it can feed into whichever corner of the suite's dictionary, token, or file-handling tools wants that specific shape.

Why this is plumbing, not a feature

It's the text-world twin of Number to Text elsewhere in the suite - unglamorous, but the kind of node that quietly unblocks a connection that would otherwise refuse to wire up. You'll typically reach for it after ComfyUI's own type-checking already told you a wire wouldn't connect: you've got a STRING coming out of a primitive, another pack's node, or a loaded file, and the WAS node you want to feed it into is declared to want its own text type instead. Rather than rebuilding the value with a WAS-native text node from scratch, String to Text converts what you already have.

How it works

A straight type conversion - the string content itself doesn't change, only the socket type it travels in. STRING goes in, WAS's text type comes out, ready to feed the pack's dictionary nodes, token system, or Save Text File chain.

The inputs and outputs that matter

One STRING input, one text-typed output. If both ends of a wire are already WAS nodes that agree on type, you'll never need this node - ComfyUI's own connection rules won't even let you make an invalid link in that case. This is specifically for crossing the boundary between a generic STRING and WAS's internal text conventions.

Installing it

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

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

install requirements.txt against your ComfyUI Python, restart. No model, no dependency specific to this node.

Common issues & troubleshooting

A wire still won't connect after adding this node. Confirm you're actually looking at a STRING-to-WAS-text mismatch and not some other type pairing entirely - this node solves one specific conversion, not every type error you might run into in a mixed-pack graph.

Not sure whether I even need this node. If a WAS text node's input socket accepts a plain STRING directly, you don't - this only matters when the target explicitly wants WAS's own text type and ComfyUI's connection check is refusing the direct link.

Whole pack fails to import. WAS Node Suite has been unmaintained since the author marked it retired in December 2023, and the recurring failure since is the entire suite throwing "Import Failed" after a ComfyUI update because a pinned shared dependency got bumped underneath it. Reinstall requirements.txt against the correct, embedded Python interpreter and restart - this node has nothing of its own to break.