Blender Output String

Not every workflow output is pixels. Sometimes you want to know what the graph decided - the prompt that actually ran, a filename it built, a value a math node computed, the path of a saved model. BlenderOutputString is the pack's text readout: it takes any value, converts it to a string, and shows it as a text output in the Blender add-on. The pack describes it as "preview any input value as text," and that's exactly the job.

It's a subclass of ComfyUI's PreviewAny node with one socket renamed - the native node's source input becomes string here, and execute just forwards it through the parent's preview path. In a pure ComfyUI graph it behaves like a preview/debug node; in the Blender bridge it becomes a text output you can read on the panel after a run. It also passes the string through on a STRING output socket, so you can preview and feed the value onward if you want.

Inputs and outputs

• string - the value to display. The socket is any-type, so you can wire in numbers, strings, or anything else and it'll be stringified for display.

Output is a single STRING, carrying the value onward if you need it elsewhere.

Installing it

Standard for the pack. ComfyUI side, ComfyUI Manager → search "ComfyUI-Blender", or:

cd ComfyUI/custom_nodes
git clone https://github.com/alexisrolland/ComfyUI-Blender

Restart ComfyUI. No extra Python dependencies, but you need a current ComfyUI - schema v3 nodes and the README says latest is required. The Blender add-on is the other half, a ZIP from the latest release installed via Edit > Preferences > Add-ons > Install from Disk.

Where people get burned

The obvious one: it's a display node, not a saver. Wire it to something and it shows text; it won't write a file or persist anything. Second, any-type inputs get stringified with whatever str() does to them - a tensor wired in here will display as an object repr that's useless for reading, so point it at strings, paths, and numbers, not pixel data. Third, like every node in this pack, the panel readout only exists after an API-format export and import into the add-on; and remember the readout reflects the last run, so a stale value usually means the workflow hasn't been re-run since a change. It's a tiny node, but in a Blender-driven workflow it's often the only way to see what the graph is actually thinking without leaving the viewport. VRAM cost: nil.