Eden_String

Eden_String is the least impressive node you'll ever meet, and it earns its keep precisely by being boring. It's a multiline text box with one input (value) and one output (STRING). Type text, get text. That's the spec.

So why does it exist, and why would you use it? Because in ComfyUI, text you type into a node's widget is trapped inside that node. You can't make another node read it. The classic annoyance is a prompt you want to use in two places, or a negative prompt shared across several samplers, or a text parameter (a filename prefix, a caption, a title) that drives multiple steps of a workflow. Eden_String turns typed text into a first-class wire, so the string becomes data other nodes can consume and transform.

It ships in eden_comfy_pipelines, Eden.art's MIT-licensed 70+ node suite, filed under Eden 🌱/Logic.

Where the pattern pays off

The real power isn't the node alone - it's what you chain it into. Wire Eden_String into Eden_StringReplace or Eden_Regex_Replace to clean it up, then into a filename builder, a save node, or a GPT node. Now your whole pipeline is driven by one box you edit in one place, and every downstream piece recomputes when you change it.

It also shows up as a building block in bigger workflows: a single string that seeds both a prompt and an archive filename, so the two can never drift out of sync. If you've ever saved an image whose filename stopped matching its prompt after an edit, you know exactly why this pattern matters.

Multiline matters too. Because value is multiline, you can paste whole prompt blocks, paragraph-length captions, or a chunk of text you're going to post-process - not just single-line labels. That makes it a decent general-purpose "text constant" node for any workflow that manipulates larger strings.

What it doesn't do

Worth being honest about: for most people, ComfyUI's built-in text nodes and the primitive String node cover the same ground, and this node adds no magic. Reach for it because you're already in the Eden pack and you want one consistent text primitive across your graph, or because you specifically need a wireable multiline string. It's a lifestyle node, not a feature node. If you only ever type a prompt into a CLIP text encode widget, you can skip it.

Installing it

Standard pack install - ComfyUI Manager (search "eden"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/edenartlab/eden_comfy_pipelines.git
cd eden_comfy_pipelines
pip install -r requirements.txt

Restart ComfyUI. No models, no API keys, no dependencies beyond the pack itself - it's a string, it doesn't need anything.

If you're assembling a workflow where the same text feeds prompts, filenames, and logging, this is the node that stops you from retyping it in three places. Boring, on purpose, and useful.