CC Text Input

CC Text Input is a text box that passes text through. One input, one output, no processing beyond stripping whitespace, no API calls, no cost. That's the whole node - and if it feels too trivial to be worth an article, that's kind of the point. It exists because of a workflow-design choice the rest of this pack makes: everything is wired, nothing is typed into widgets twice.

Why it's there

Look at the reference workflow in Auto-Card-Generator and you'll see the same shape: a few CC Text Input nodes at the top feeding the prompt builder, the chunk planner, and the request builder. Your script, your creative brief, your hard constraints - they're all text boxes at the head of the graph, because a value that flows through wires can be changed once, reused in several places, and pointed at from anywhere. Type your idea into a bare widget and it's stuck in that one node; put it in a text-input node and you can branch it to three consumers and still edit it in one place.

It also supports ComfyUI's dynamic prompt syntax (the dynamicPrompts flag is on), so you can use things like wildcard-style {option|option} expressions in the text - handy for batch runs where you want each generation to pick a variant.

The one input, the one output

• text (in) - your script, brief, or any string. Multiline, so paste freely.
• text (out) - the same string, stripped. Wire it into CC Prompt Builder's user_prompt, CC Script Chunk Planner's script_text, CC Kling Request Builder, or anywhere a string is expected.

There's nothing to configure, nothing to get wrong, and nothing to troubleshoot. If it ever seems broken, you're almost certainly looking at the node it feeds, not this one.

Installing it

Part of the Auto-Card-Generator pack by mircudx (MIT, no pip dependencies, no models to download). Install via ComfyUI Manager by searching "Auto-Card-Generator", or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/mircudx/Auto-Card-Generator

Restart ComfyUI and it appears under "Card Creator/LLM". If you're importing a bundled workflow and hit missing-node errors, grab the *_local_safe_compat.json version - it's built for bare local installs.