➡️ IG Int

IG Int is the simplest possible node: a value box and a wire out. You type an integer, it outputs that integer as an INT. ComfyUI already ships primitive nodes that do roughly this, so why would this pack bother? Because a dedicated typed primitive has one advantage in a graph: it produces a genuinely typed INT output, and several nodes in this pack (and others) use forceInput fields where the wire type has to match exactly. A plain primitive can drift into being treated as a float or a string depending on context; this node can't.

In practice it's the cleanest way to feed a hard-coded integer into nodes that want a specific value - a seed, a frame count, a max_images cap, an index. There's a school of thought that says inline numeric widgets on the node you're targeting are enough, and for a single value that's true. Where IG Int earns its keep is when the same constant feeds several nodes: wire it once, change it in one place, and every consumer updates. That's a real workflow-legibility win, not just ceremony.

Inputs and output:

• value - INT, default 0, range effectively unbounded (sys.maxsize both ways), step 1.
• Output: INT - the same value, untouched.

It's a pass-through. There's no clamping, no conversion, no side effects. The node class is five lines of Python in nodes/primitives.py; the value in the box is the value on the wire, full stop. Because there's no logic, the only way to get it wrong is to set the wrong number.

Install is the shared pack routine:

cd ComfyUI/custom_nodes
git clone https://github.com/IDGallagher/ComfyUI-IG-Nodes
cd ComfyUI-IG-Nodes && pip install -r requirements.txt

Or ComfyUI Manager → search "IG Interpolation Nodes" → Install, then restart. No dependencies beyond the pack baseline, no models. It shares a category (🐓 IG Nodes/Primitives) with IG Float and IG String, its twins for the other two primitive types - grab those when a field wants a FLOAT or STRING constant wired the same way.