Nodes/StudioDeep/String Template
ComfyUI Node

String Template

A template that's mostly a placeholder — literally

By studiodeep-ai·Created 6 months ago·Updated 5 months ago· 0
String Template
    • text
    template

    Let's be straight about String Template: in its current shipped form, this node is mostly a promise. The code clearly wants to be a templating engine - it takes a template string and substitutes {{placeholder}} patterns with values - but the version you get today exposes exactly one input, template, with no fields to feed it. So the substitution machinery runs against an empty set of values, and what comes out the text output is effectively the template unchanged. It's a text holder that's honest about being a text holder.

    That's not a bug you need to work around. It's a node that's waiting on its next version, and knowing that saves you the half hour I spent wondering where the placeholders were supposed to come from. If you're building a workflow today and need string interpolation with real values, use a text-concat or format node from another pack - or the pack's own T2V Prompt Builder, which does the actual structured assembly.

    How it works

    Mechanically: execute() takes the template and does result.replace("{{key}}", str(value)) for every key passed in - then returns the result. The schema just doesn't pass any keys in this release, so the replacements never fire. Read the code and you can see where it's headed: a template string with {{shot}}, {{lighting}}, {{subject}} hooks, and inputs that supply them. It's an unfinished socket waiting for its pins.

    Inputs: template (multiline string). Output: text (STRING).

    Installing

    Same as the rest of the pack:

    cd ComfyUI/custom_nodes
    git clone https://github.com/studiodeep-ai/comfyui-studiodeep StudioDeep
    pip install -r StudioDeep/requirements.txt
    

    or search "StudioDeep" in ComfyUI Manager, restart. No keys or models.

    Troubleshooting

    • {{anything}} isn't being replaced - that's the shipped behavior, not a misconfiguration. There are no value inputs in this release.
    • You need real templating now - grab a dedicated string-format node from the registry (plenty exist) or route through the T2V Builder. Come back to this one when the pack adds the inputs it clearly intends to.

    The kind take: every pack ships a node that's one release ahead of itself, and this is StudioDeep's. Worth a star in your mental "check back later" list, worth skipping for today's workflow.

    CategoryStudioDeep

    Inputs (1)

    NameTypeDefaultDescription
    templateSTRING

    Outputs (1)

    NameTypeDescription
    textSTRING