Text Prompt Builder (Legacy)

This is the original Text Prompt Builder, before the pack learned to grow its own input slots. Where the current node gives you unlimited variable_1, variable_2, … inputs, this one is welded to exactly four: variable_a through variable_d. Same job, same template engine, hard cap of four variables. The "(Legacy)" suffix in the node menu is the pack admitting this is the old way - it's kept around so workflows saved on the earlier version still load without missing-node errors.

How it works

Identical mechanism to the dynamic version. The template input (multiline, defaults to {subject}, {style}) is filled in with values from the connected variables, and the node returns a string. You reference variables by the name from a Text Prompt Node ({subject}), by full slot ({variable_a}), or by short suffix ({a}). Unconnected slots become empty strings, so a template that names a slot nobody plugged in just renders a gap.

One difference from its modern sibling: the legacy input slots are typed as * - they accept anything, not just PROMPT_VAR. A raw string will be treated as its text, which is slightly more forgiving than the dynamic node's cleaner strictness.

The four-slot reality

The fixed slots are the whole story, and they're why you shouldn't install this for anything new. Four variables is plenty for subject + style + lighting + camera, but the moment you want a fifth block you're rebuilding your workflow. The dynamic Text Prompt Builder does everything this does with no slot ceiling, and it's the same install either way - there's no reason to reach for the legacy version unless you're loading an old workflow and don't want to rewire it, or you genuinely like having your slot count pinned down.

Installing it

Same pack as everything else in ComfyUI Prompt Builder. ComfyUI Manager: search "ComfyUI Prompt Builder", or:

cd ComfyUI/custom_nodes
git clone https://github.com/aimoviestudio/comfyui-promptbuilder

Restart ComfyUI. The pack has no Python dependencies and downloads no models, so this is as friction-free as custom node installs get.

One thing to keep in mind: because legacy nodes exist purely for backward compatibility, they're the first thing a maintainer drops when the pack gets a major cleanup. If you're building something that'll outlive this week, use the dynamic node and let this one fade into the saved-workflow museum it's designed to be.