easy string

There isn't much to easy string and that's the point: it's a single-line text box that outputs a STRING. No prompt encoding, no multiline text, no formatting - just a literal value you can wire into anything expecting text.

Why you'd reach for this instead of hardcoding a value. ComfyUI nodes often have a text field baked directly into their widget - you type a filename prefix right on the Save Image node, say. That's fine until you want the same value in two places, or you want to swap it out from a for-loop, or you're building a graph where the value should come from logic elsewhere rather than being typed by hand on every node that needs it. easy string turns a literal into a proper wire: type it once here, and connect that output to every socket that needs the same text - a filename, a key for a switch/routing node, a fragment you're concatenating elsewhere, or an override going into easy pipeEdit's prompt inputs.

Where it sits in the pack. The category - EasyUse/Logic/Type - tells you this is part of a small family of typed-constant nodes (this one for text; the pack has equivalents for other primitive types). They exist for the same reason typed literals exist in any programming language: sometimes you need a value's type to be explicit and consistent on the wire, not just correct by coincidence because ComfyUI's loose typing let it through.

Input and output. One required input, value - a single-line STRING widget, default empty. One output, string. That's the entire node.

Why the type matters more than it looks like it should. Easy-Use's logic category leans on strict-ish typing to make switch and comparison nodes behave predictably - a easy string output is unambiguously a STRING socket, so a switch node routing on text, a concat node building a longer string, or a compare node checking equality all know exactly what they're getting. Contrast that with typing a value straight into a downstream widget: some ComfyUI widgets happily accept a typed number and silently coerce it to text (or vice versa), which is exactly the kind of subtle mismatch that produces a workflow that runs without erroring but does the wrong thing. Routing everything through an explicit easy string first is cheap insurance against that.

Install. ComfyUI Manager (search "ComfyUI Easy Use") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

then restart. No dependencies - this is pure logic, nothing to break.

Common issues. Honestly, not much goes wrong here. The one thing worth flagging for beginners: this is single-line only. If you need a multi-line prompt or block of text, this isn't the node - reach for a proper multiline text node (or the prompt fields on easy pipeEdit) instead, since jamming a paragraph into a single-line widget either truncates visually or just makes for an unreadable node. Use easy string for the short, structural stuff - filenames, keys, tags - not for prose.