Template Input
A big text box for your prompt template (that's genuinely all it is)
- template_out
Template Input is a string node that doesn't transform anything. You type into it, and it hands the exact same text back out. That sounds pointless until you remember what most ComfyUI prompt plumbing looks like: strings get assembled inside little single-line text boxes and glued together with Combine Text nodes, and after a while you can't tell which node holds the actual sentence. This node exists to give your template a visible, editable home.
It's the middle of this pack's three-node template system, and it's worth seeing how it slots in: Item List defines a named set of options, Template Input holds the template with {placeholders} in it, and Template Processor picks the options and fills the placeholders. Template Input's only job is to be the place where you write Today is a {adjective} day. and keep it somewhere you can actually find.
Inputs and output
template- the only input, a multiline STRING defaulting toToday is a {adjective} day.. Multiline matters; this is your prompt body, and most prompt templates are longer than one line.template_out- the output, the same string, untouched.
The mechanism is literally return (template,) - pass-through, nothing cached, nothing parsed. The default value is a nice hint at how the pack expects you to use it: write the sentence, leave the {bracketed} slots for the Processor to fill.
Why you'd bother
Two honest reasons. First, graph readability: a big labeled text box that says "the template" beats a tiny input field on an unrelated node when you come back to a workflow six weeks later. Second, it decouples the template from the processor - you can wire the same template_out into several processors, or swap templates without touching the rest of the graph.
That's also the honest catch: this node adds no capability. Any node that outputs a string works here, and if you already have a text node you like, you don't need this one. Don't install the pack for it alone - install the pack for the Processor, and treat this as the convenient spot to park the template string.
Installing it
Same pack as the rest of the zygion utilities: no dependencies, no model files, stdlib only. ComfyUI Manager - search i-zygion-util-nodes - or:
cd ComfyUI/custom_nodes
git clone https://github.com/zygion/comfyui-zygion-util-nodes
Then restart ComfyUI. It appears under Zygion Custom Nodes.
Troubleshooting
There's almost nothing that can fail here, so the only "issue" is a misread of what it does. If you wire Template Input straight into a CLIP Text Encode and see {adjective} in your generated prompt, that's not a bug - this node deliberately does not fill placeholders. It's a carrier. The replacement happens one node downstream, in the Template Processor, and only if its vars input is connected and the names line up. If you keep seeing braces, that's where to look, not here.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| template | STRING | Today is a {adjective} day. | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| template_out | STRING | — |