Blender Input Boolean

This node is how you hand Blender a checkbox. The whole point of ComfyUI-Blender is that you build your workflow once in ComfyUI, then drive it from a panel inside Blender - and every BlenderInput* node in the graph becomes a control on that panel. BlenderInputBoolean becomes a checkbox: on/off, no typing required. It's the simplest input node in the pack and the one you'll reach for whenever a workflow has a toggle you don't want to dig into ComfyUI to flip - enable the ControlNet, turn on the hires pass, switch img2img on and off for a batch of camera angles.

The mechanism is deliberately boring, which is the point. The node subclasses ComfyUI's built-in Boolean primitive, so in a pure ComfyUI graph it just passes whatever value it holds straight through. All the extra inputs exist to configure the checkbox that the Blender add-on renders. That's the mental model for the whole pack: in ComfyUI these nodes do almost nothing, because the actual UI lives on the other side of the bridge.

Inputs and outputs

Only three inputs matter, and two of them are configuration:

• value - the boolean the node outputs. In Blender this is whatever the checkbox is currently set to.
• default - what the checkbox starts at when you first load the workflow. A "high detail" toggle that should be on by default? Set this to true.
• order - position of this control in the Blender panel. Lower numbers float to the top. In the add-on, controls stack in this order, so 0, 1, 2 is the sequence you usually want.

There's also an optional group input. Wire it to the group output of a Blender Input Group node and the checkbox gets drawn inside that group's box in the panel. It's purely cosmetic, but on a panel with a dozen controls it's the difference between usable and "where the hell is the toggle."

Output is a single BOOLEAN, which feeds anything downstream expecting a boolean - a ControlNet's enabled flag, a condition switcher, a batching node.

Installing it

This is the whole pack, not just the node. On the ComfyUI side, search "ComfyUI-Blender" in ComfyUI Manager and install, or clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/alexisrolland/ComfyUI-Blender

Restart ComfyUI. The pack has zero extra Python dependencies (its pyproject.toml declares none), so there's no pip dance. The one real requirement is a recent ComfyUI - the pack moved to the custom-node schema v3, and the README is explicit that older versions won't load the nodes.

The Blender side is a separate add-on, a ZIP from the latest release installed via Edit > Preferences > Add-ons > Install from Disk. The add-on and the nodes are two halves of the same bridge; without the add-on, this node is just a toggle in a ComfyUI graph.

Where people get burned

The common trap is expecting the node to do something visible in ComfyUI. It won't. The add-on only builds its panel from the nodes after you export the workflow in API format (File > Export (API)) and import it into Blender - and the node's title becomes the label next to the checkbox, so name it something a human would actually read ("Enable ControlNet", not "toggle2"). If the checkbox doesn't appear, the usual suspects are an outdated ComfyUI (schema v3 won't load) or the server not running with --listen when Blender is on another machine. And if you're running Blender and ComfyUI on the same GPU, remember the viewport is eating VRAM - the checkbox is free, the render behind it isn't.