textInput
The boring pass-through where your users' words enter the graph
- STRING
The most boring node in this pack is also one of the most important in a converted app. sdBxb_textInput (display name "textInput") takes a string and hands it back to you untouched. That's it. There's no parsing, no transformation, no cleverness - you type into the box, and the same text comes out the other end.
So why does it exist? Because in the pack's design, this is the marker for where end-user text enters your workflow. When you wrap a graph into a WeChat or Douyin mini-program with the sdBxb node, the text fields your customers fill in - "enter a prompt," "describe what you want" - need somewhere to land in the graph. This node is that landing spot: the app's typed input feeds into it, and it passes the words along to whatever you wired it into. It also pairs with the custom_text1–3 inputs on the sdBxb config node, which expect forced string inputs from elsewhere in the graph.
The input and output
text(STRING, multiline) - the only input. Type or wire in your text.- STRING output - the same text, unchanged.
You could absolutely replace it with any other text primitive in a normal workflow and nothing would break. Its value is consistency and clarity: in a conversion workflow, seeing a textInput node tells you (and the backend) exactly where user text should land. If you're building a paid mini-program from a ComfyUI graph, you'll want a couple of these sitting around so your customers can drive prompts or settings without you hard-coding every value.
Installing it
It ships with the ComfyUI_Bxb pack - ComfyUI Manager (search ComfyUI_Bxb), or:
cd ComfyUI/custom_nodes
git clone https://github.com/zhulu111/ComfyUI_Bxb
Restart ComfyUI and it's there. No model downloads, no extra GPU footprint; this node is pure data plumbing. Worth remembering the pack-level caveat, though: the pack's free cloud conversion service was retired in January 2026, so the full mini-program pipeline today runs through the paid private-deployment version. This node itself is harmless either way - it just moves text around, completely offline.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |