String (for Interactive)

InteractiveString is the plain-text member of the pack's small set of literal nodes - you type a string into the widget, it comes out as a STRING output, and that's the entire node. It sits next to InteractiveInteger and InteractiveFloat for the same reason: the author frames all three as literals meant to travel cleanly through a workflow built around InteractiveSelector and InteractiveSwitch, rather than assuming a generic string primitive behaves identically once it's part of a paused, click-driven graph.

Where this actually earns a slot on your canvas is feeding a parameter_string on an InteractiveSelectorWithParameters node - one InteractiveString per branch, each holding a different label, tag, or short caption, so whichever branch gets clicked, its string comes along with it and appears back out of the matching InteractiveSwitchWithParameters.

How it works

There's no transformation happening - type text in, get the same text out, every execution. If you need to build a string up from more than one literal (say, combining a base prompt with a branch-specific tag), that's not this node's job; that's what InteractiveStringAppend is for. This node is strictly a single, static value holder.

The inputs and outputs that matter

• string (required, STRING, default "") - the text itself, entered directly in the widget. This is a single-line field, unlike InteractiveStringMultiline.
• string (output, STRING) - wire it into a parameter_string on a selector-with-parameters, a CLIPTextEncode, or anywhere else expecting text.

One field, one output. If you're picturing something more elaborate, this isn't it - that's by design.

How to install it

Part of the full pack install. Via ComfyUI Manager: search "ComfyUI-Interactive". Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/lquesada/ComfyUI-Interactive

Restart afterward. No requirements.txt, no model files.

Common issues & troubleshooting

My text has line breaks and they're getting cut off or mangled. This node is the single-line variant - use InteractiveStringMultiline instead if you need multiple lines. They're separate nodes on purpose; InteractiveString is meant for short labels and tags, not paragraphs.

Why not the stock string primitive? For a non-interactive part of your graph it makes no practical difference. Inside the paused/click-driven section of a workflow, the author's own guidance is to use the pack's matching nodes - they're built and framed specifically for that execution pattern, and it keeps that section of the graph internally consistent.

The value looks stale after I edit it. Same pack-wide caveat as everywhere else: keep auto-enqueue off and the queue empty. Editing a widget mid-run can leave you looking at a value from before the edit landed.

I want to combine this string with another one. That's not what this node does - reach for InteractiveStringAppend, which takes two string inputs and a chosen separator and outputs the joined result. It exists specifically because a popular alternative (Custom-Scripts' "String Function" node) has a display bug in interactive workflows that slows things down.