flow_judge_input

This is a two-input if/else selector: give it a true candidate, a false candidate, and a boolean to decide between them, and it forwards whichever one matches onto a single data output. It's the mirror image of flow_judge_output, which is elsewhere in this pack - that one takes one value and routes it to one of two outputs based on a condition; this one takes two candidate values and merges them into one, based on the same kind of condition.

How it works

Wire whatever you want used when the condition holds into true, and whatever you want used otherwise into false - both are wildcard-typed, so images, strings, latents, anything works. Set judge (a plain boolean, defaulting to true) yourself, or - more usefully - feed it from an upstream boolean-producing node like flow_case_tentor (image-shape and size conditions) or flow_ChangeDetector (stability conditions), also in this pack. Whichever of true/false matches the current value of judge gets passed through to data.

It's a small node, but it's the kind of thing that turns "I have two versions of this and I want to pick one based on a condition" into a single wire instead of a tangle of reroutes - the sort of ergonomics this whole pack is built around, per its own README framing of simplifying dense, hard-to-follow workflows.

Inputs and output

• judge (BOOLEAN, required, default true) - the condition.
• true (optional, wildcard) - used when judge is true.
• false (optional, wildcard) - used when judge is false.
• data (output, wildcard) - whichever candidate matched.

Installing it

Search ComfyUI-Apt_Preset in ComfyUI Manager and install, or manually: cd ComfyUI/custom_nodes && git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git, then restart. The README's dependency step is "double-click install.bat" - a Windows-first instruction, with no requirements.txt visible elsewhere, so on Linux/Mac open that file to see what it installs and replicate it manually in your ComfyUI venv. This node is pure logic and needs none of the pack's optional extras (GGUF, Advanced-ControlNet, nunchaku, downloaded models).

Common issues

Both true and false are optional inputs - if you leave the one that matches your current judge value unconnected, data will have nothing real to forward, and whatever's downstream is likely to error or silently receive a null. Make sure the branch you expect to actually fire has something wired to it.

Since both sockets are wildcard-typed, ComfyUI won't check that your true and false values are even the same kind of thing - it's on you to keep them consistent (both images, both strings, whatever your downstream node expects), since mismatched types will only surface as an error once the graph actually runs.

And the general pack caveat: this is one node inside a large, actively developed package where an import error anywhere can take the whole pack - including this node - offline. If it's missing after install, check the ComfyUI console at boot for the real traceback before troubleshooting your workflow.