STRING

A single-line text field that outputs whatever you typed. That's it - the plainest node in a pack full of small utility primitives, and the one you reach for when a value is short: a filename, a label, a key for JN_KeyValue, a save-prefix, a single tag. If you need several lines, this isn't the one - the pack's own JN_PrimitiveStringMultiline and JN_PrimitivePrompt handle that.

It's part of JNComfy (jn-jairo/jn_comfyui), a one-person pack covering everything from voice conversion to face restoration to this family of small logic and value primitives. It has essentially no presence in the wider community - no threads, no discussion - which means the README and the node's own schema are the complete reference, not a starting point for a bigger search.

How it works

Nothing to explain, honestly. value is a plain text field with an empty default; the node outputs it as a STRING, unchanged. The single-line widget in the UI is a hint about intended use, not an enforced limit - nothing stops a wire from feeding it something long, the widget just renders it as one line.

Where this earns its keep is less about what it does and more about where it sits: as one of the pack's own Primitive nodes, it plugs cleanly into JN_PrimitiveToString, JN_KeyValue, and the array family without any type friction, because they're all built around the same generic-typing conventions documented in the README. A bare ComfyUI STRING widget would work too for a standalone value - the payoff for using JN's own version shows up once the rest of your graph is already leaning on the pack.

The inputs and outputs that matter

• value (required, STRING, default empty) - the text.
• Output: STRING - the same text.

Installing it

ComfyUI Manager: search "JNComfy". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/jn-jairo/jn_comfyui

Restart ComfyUI. No models, no dependencies.

Common issues & troubleshooting

Not sure whether to use this or ComfyUI's built-in STRING primitive. For a bare value there's no functional difference. The reason to reach for JNComfy's version specifically is consistency with the rest of the pack - its To* conversion nodes, JN_KeyValue, and the array family all share the same generic-typing patches, so staying inside one family avoids any friction at the edges.

You pasted multiple lines in and it looks fine, then breaks something downstream. The single-line widget doesn't actually strip or reject newlines if they got in there via paste or a wire - if a downstream node behaves oddly on what should be a short label, check whether the string secretly contains a line break you didn't notice.

Trailing whitespace causing a mismatch. If this value is feeding into something doing an exact string comparison (a filename check, a key lookup), a stray trailing space typed into the widget is an easy, invisible cause - nothing in this node trims it for you.