Int (RE)
A labeled integer you can wire to more than one place
- int
There's nothing to figure out here - this node holds one integer and hands it back out. No math, no clamping beyond what you type in, no side effects. Its entire reason to exist is letting you park a number as its own labeled node instead of burying it as a bare widget on whatever downstream node happens to need it.
That's more useful than it sounds once a workflow gets big. Say a batch size, a step count, or a seed offset needs to feed three different nodes scattered across your canvas. Instead of typing the same number into three widgets and keeping them in sync by hand every time you change your mind, you set it once here and wire the single INT output wherever it's needed. Rename the node (right-click → Title) to whatever the number actually means - "refiner steps," "grid columns" - and your graph starts reading like documentation instead of a pile of unlabeled boxes.
It's also shaped to match this pack's own RErouter bus. Several of that node's output sockets - INT1, INT2, INT3, SEED - are exactly this shape: a plain integer with nowhere else to originate from except a node like this one, upstream of whatever packs values onto the bus in the first place.
The inputs and outputs that matter
- int - the value itself, a plain integer widget, defaulting to 0.
- int (output) - the same value, passed straight through, typed INT so it wires into anything expecting a normal integer: step counts, batch sizes, seeds, whatever the graph needs.
How to install it
Same repo as the rest of this pack - ComfyUI Manager, search ComfyUI_RErouter_CustomNodes, install, restart. Or manually:
cd ComfyUI/custom_nodes
git clone https://github.com/an90ray/ComfyUI_RErouter_CustomNodes.git
then restart. Nothing to download, nothing else to configure - a node this small has no dependency surface to worry about.
Common issues & troubleshooting
There's genuinely not much that goes wrong with a node this small, but two things trip people up:
"Why not just use ComfyUI's built-in Primitive node?" You can, and for most workflows it does the same job. Reach for this one specifically if you're already using the rest of the RErouter pack and want your utility nodes to match the family, or if a downloaded workflow already has it in place. Otherwise there's no real reason to install a whole extra pack just for this one node.
No feedback if the value is wrong for what it's feeding. Since there's no validation beyond ComfyUI's normal number input, a value that's technically valid but wrong for its purpose - a batch size of 0, a negative step count - passes straight through and fails wherever it's actually used, not here. If a downstream node errors mysteriously, trace back to see if an Int (RE) node upstream is holding something unexpected before you go looking anywhere else.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| int | INT | 0 | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| int | INT | — |