Ino Int To String

This is a boring node, and I mean that as a compliment. It takes an integer and gives you back its string form. That's the entire job: one input, input_int, one output, string. You won't write a forum post about it, but you'll reach for it constantly once you've built a workflow that assembles filenames, batch names, or display text from numbers.

Where it earns its keep is in automation. ComfyUI is strict about types - an INT from a random node or a counter won't silently slot into a string input, so when you want to build something like batch_7.png from a computed batch index, you need an explicit conversion. This node is that conversion, with zero surprises. It literally calls str(input_int).

When you'd actually use it

• Concatenating an int into a filename or a Save Text payload.
• Building display strings for a UI node so you can see what a computed value was without squinting at a number port.
• Plumbing ints into prompt assembly or JSON-building nodes that expect strings.

The thin utility nodes in this pack are all like this - no state, no downloads, no GPU work, just one small well-defined transform. If you don't need it, you don't need it, but when you do, it's the difference between a working graph and a type-mismatch error.

Inputs and outputs

• input_int (INT) - the number to convert. Defaults to 0.
• string (STRING) - the output, e.g. 42 becomes "42".

No padding, no formatting options. If you need leading zeros, that's a different node (see Ino Random Int In Range for a length-padded string output), and if you're converting from a float, cast that first.

Installing it

This ships in the ComfyUI-InoNodes pack (Inoland, 125+ nodes). ComfyUI Manager → search "ComfyUI Ino Nodes" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/nobandegani/comfyui_ino_nodes
cd comfyui_ino_nodes
pip install -r requirements.txt

Restart after. Requires inopyutils (auto-installed) and a recent ComfyUI on the V3-style node API.

Common issues

Honestly, the failure modes here are "you wired it into something expecting a different type anyway" - if the downstream node won't take the string, the problem is downstream, not this node. The one thing that trips people: an int from a randomized seed input isn't a static value, so if you feed a seed into this and wonder why the filename keeps changing, that's the seed doing its job. Everything else is as boring as promised.