🔢 Integer Input

The integer twin of the pack's ArchAi3D_Float_Input, and it earns its keep the same way: the name field. ComfyUI desktop users get a bare int widget; users running the workflow through a web interface get a properly named, min/max/step-validated form field that frontends can render as a slider or number input. If you're building template workflows for other people to fill in, this is how you make "steps" and "seed" and "tile_width" look like a form instead of a graph.

Inputs

• name - the identifier for web interfaces; becomes the field label. Default int_input.
• value - the integer out. Default 0.
• min / max - validation bounds (full 32-bit range by default, ±2^31). The web form and the widget slider respect these.
• step - increment, default 1. Min 1, max 1,000,000, so it handles both fine-grained and coarse adjustments.

Output: an INT. Feed it to any integer slot - steps, seed, tile sizes, width/height, batch count.

The honest take

Same verdict as the float version: if you're alone in the desktop app, this is a redundant convenience and you can use any stock constant node. It earns its place in two situations - building shareable template workflows where a named input makes the graph self-documenting, and running workflows through a web frontend where you want users to see exactly which knobs exist. The pack's input family (String, Int, Float, Boolean) keeps the style consistent, so a workflow built on this pack has a uniform "what to fill in" layer.

One small thing it does better than some stock nodes: it pairs min/max with the value, so a web form can't let someone type 999999 into your steps field. That's the kind of guardrail that matters when the person running the workflow isn't you.

Install

Same pack, no dependencies:

cd ComfyUI/custom_nodes
git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git

Restart ComfyUI, look under ArchAi3d/Inputs. Free personal, paid commercial - the standing license note for everything in this pack.