Nodes/PixelML ComfyUI Nodes/StringInput_PixelML
ComfyUI Node

StringInput_PixelML

A named string input — a label for the text that flows through your graph

By PixelML·Created 2 years ago·Updated 2 years ago· 0
StringInput_PixelML
    • STRING
    namestr_input
    value

    StringInput_PixelML is the plainest member of the PixelML pack: a name field, a value field, and a STRING output that passes the value straight through. No parsing, no clamping, no fallback - a string doesn't need any of that. It's the text version of the pack's boolean toggle, and it exists for the same reason: to give a value a label in workflows that are built or driven by automation.

    Here's the thing about core ComfyUI: it already gives you string primitives, and for hand-typing a prompt or a filename, the built-in approach is fine. Where this node earns its keep is the name field. In a graph where an agent or a script is reading node names to figure out what each input means, "str_input" vs "brand_name" is the difference between a mystery wire and a self-documenting graph. That's the whole pitch, and it's a modest one.

    It comes from PixelML ComfyUI Nodes, a small collection focused on variable handling and workflow automation. Like its siblings, the value can be wired in from anywhere - another string node, a wildcard processor, an LLM output - and it'll pass whatever text arrives.

    How it works

    The implementation is a one-line pass-through: get_value returns value. That's it. There's no stripping, no escaping, no multiline handling beyond whatever the widget itself allows, and no type conversion. What you set or feed in is exactly what comes out.

    That simplicity is the point. It's the string version of a named constant - a single, labeled source of truth for text that other nodes consume, so you don't have five prompt nodes scattered across the graph all carrying different copies of the same phrase.

    The inputs

    • name (STRING, default "str_input") - a label for agentic bookkeeping. It doesn't touch the output.
    • value (STRING, default "") - the text itself. Type it or wire it in from another node.

    The single STRING output goes to any text input: a CLIP text encoder, a filename prefix, a URL, a JSON payload builder.

    Install

    Easiest via ComfyUI Manager - search "PixelML ComfyUI Nodes", install, restart. By hand:

    cd ComfyUI/custom_nodes
    git clone https://github.com/PixelML/ComfyUI-PixelML-CustomNodes
    

    Then restart ComfyUI. Same caveat as every node in this pack: the requirements.txt pins diffusers==0.24.0 and lists boto3/httpx/httpx-sse, none of which the shipped code imports. A string pass-through needs only what ComfyUI already bundles. If the requirements file causes a diffusers downgrade that breaks other nodes, you can skip it - and you should, because nothing in this pack actually runs diffusers.

    If all you need is a text input you can type into, the core String primitive is perfectly fine and you don't need this pack. Grab StringInput_PixelML when a workflow is being assembled or driven programmatically and the label matters more than the mechanics.

    Categorysd

    Inputs (2)

    NameTypeDefaultDescription
    nameSTRINGstr_input
    valueSTRING

    Outputs (1)

    NameTypeDescription
    STRINGSTRING