ComfyUI Node

IntPass

The most honest node in the pack

By robertvoy·Created 2 years ago·Updated 9 months ago· 239
IntPass
    • INT
    INT

    IntPass takes an integer and gives it back to you. That's the whole node. No processing, no conversion, no hidden state - the source is literally return (INT,). It's the integer member of the pass-through family the Flux Continuum pack ships (PipePass for pipes, LatentPass for latents, SEGSPass for SEGS), and it exists for one reason: keeping data flow intact in a giant modular workflow.

    Why a node that does nothing is worth having

    ComfyUI lets you wire any output into any compatible input, but the visual result is spaghetti. When you've got one integer (say, a seed, a batch index, or a step count) that needs to reach several places, a pass node lets you route it through a labeled waypoint instead of dragging a wire across half the canvas. It also gives you a place to park the value so you can see it at a glance, and it can sit between a slider and its consumer as a clean junction when the workflow's internal "Get_" routing needs a concrete value on the wire.

    It's the kind of node that reads as pointless until you've maintained a 200-node workflow, at which point you start appreciating the plumbing.

    Inputs and outputs

    • INT - one required integer input.

    Output is one INT, identical to the input. There are no parameters to tune, no settings, nothing. If you need a slider instead of a bare value, the pack's Batch Slider or Select From Batch produces the same INT type with a nicer control surface.

    Installing it

    It's bundled with robertvoy/ComfyUI-Flux-Continuum:

    cd ComfyUI/custom_nodes
    git clone https://github.com/robertvoy/ComfyUI-Flux-Continuum
    

    or via ComfyUI Manager ("Flux Continuum"), then restart. Zero dependencies beyond the pack itself.

    Honest assessment

    If you're building a workflow from scratch and just need to move one integer, you can skip this and wire directly. Grab IntPass when you're tidying up a large graph, when a type mismatch forces you to route through a compatible junction, or when you want a named anchor for a value that changes. It's plumbing, and plumbing is allowed to be boring.

    CategoryFlux-Continuum/Utilities

    Inputs (1)

    NameTypeDefaultDescription
    INTINT

    Outputs (1)

    NameTypeDescription
    INTINT