textInput
TextInput does exactly one thing — passes a string through — and that's fine
- STRING
Every custom node pack ships a text passthrough, and this is ComfyUI_DeployCash's. textInput has one input, one output, and no logic: you type (or wire) a string, it hands you back the exact same string. The whole implementation is return (text,). There is nothing else to it, and there doesn't need to be.
The input is text - a multiline string widget. The output is STRING, which is what every node in the pack is missing when it needs a text value. Don't expect wildcards, randomization, or dynamic prompting: it's a pipe, not a template engine. If you need wildcard or prompt-generation behavior, any dedicated text node from another pack will do that job; this one just passes bytes.
Why it exists
Look at the DeployCash node's custom_text1–3 slots: they're forceInput strings. That means they want a wire connected, not a value typed into a widget. So the pack needed a pluggable source of text, and textInput is that source. In the example workflow the pack ships, a textInput carrying "红头发" (red hair) feeds one of those custom text slots - i.e., it's how a seller wires up the text fields that buyers see and can fill in on the published app page.
In other words: it's the "connect a text source here" adapter for the DeployCash node. If you're building a workflow to publish through the pack, you'll drop a few of these in to populate the custom_text slots. If you're not publishing anything, you have no reason to touch it - the core Primitive/Text nodes do the same job and you already have them.
Install
It comes with ComfyUI_DeployCash, so install the pack and you're done. Manager: search ComfyUI_DeployCash, install, restart. Manually:
cd ComfyUI/custom_nodes
git clone https://github.com/jacklukai/ComfyUI_DeployCash
Restart ComfyUI. Dependencies are just websockets and aiohttp, auto-installed on first import - nothing to download by hand.
When it breaks
Honestly, this node is near impossible to break: no API calls, no models, no state. The one thing that trips people up is the opposite direction - connecting the output to a non-string input, which ComfyUI will refuse at the wire. And note the package's README is empty, so don't expect docs; the node's behavior is its documentation. Use it because it's already installed, not because it's special.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |