Primitive Widget → String

This node does one thing: takes whatever text is in its input widget and outputs it as a STRING. No conversion math, no parsing, no secret sauce - the entire implementation is a passthrough, and the code says as much ("Just return the input value unchanged"). It exists because ComfyUI's type system sometimes refuses to connect a string-typed widget to a string-typed socket, or chokes with "value not in list" validation errors, and a dedicated passthrough is the universal adapter that dodges all of it.

Why it exists (and why you'll keep it in a corner of your graph)

The README pitches a fancier story - "converts numeric or widget values into strings for dynamic parameter control," driving LoRA strength from sliders. The shipped code is more modest: one string input, one string output. What it's actually for is plumbing. If you're building a prompt-reactive workflow where a KeywordMatchGate output needs to flow into a node that only accepts a socket of type STRING, or a text widget keeps refusing to connect, this node is the solder joint. The class docstring even name-drops Era Styler's era selector and "a folder socket" as the kinds of widget values people keep needing to coerce.

The one real gotcha

The input is literally named folder - that's the widget label in this pack's version, and it's not a directory. If you type a path into it expecting it to read a directory, it won't; the value passes straight through untouched and comes out the text output as-is. The name is a leftover from whatever workflow this node was extracted from. Just treat it as "any text." You cannot rename the label from the graph, so if the misleading name bothers you, this may be the single most annoying node in the pack for absolutely no functional reason.

Install

ComfyUI Manager (search ComfyUI-Zlycoris) or:

cd ComfyUI/custom_nodes
git clone https://github.com/TripleHeadedMonkey/ComfyUI-Zlycoris.git

Restart ComfyUI. No models, no dependencies beyond what the pack already pulls in.

When you'd use it

• Unblocking string routing - a STRING socket refusing a widget value, or a "Value not in list" validation error on a dropdown you can't satisfy. Run the text through here and the error disappears, because the node sidesteps ComfyUI's validation entirely.
• Bridging text into logic - feed the output into a KeywordMatchGate's input_text, or chain it into any string-consuming node in your automation.
• Making a text value graph-editable - wire a string into it from elsewhere and you can keep the value alive even if the original node gets bypassed.

It's a thin utility, and it's fine to be a thin utility. Not every node in a pack needs to change your life - some just need to unstick your graph at 2am.