Boolean Flip

The simplest node in the vsLinx pack, and maybe the most underrated: it takes a boolean and inverts it. True becomes False, False becomes True. One input, one output, nothing else. But the reason an inverter is genuinely useful isn't the math - it's that in real workflows your conditions rarely arrive with the polarity you want.

Where you'll actually use it

The classic case is the inverted guard. Say you have a Forward/Mute on Boolean that should mute a branch unless a flag is set. You can't always flip the source of that flag - it might come from another node, another subgraph, or a shared workflow you don't control. Drop a Flip in between and your mute condition becomes "mute when the flag is not set", without touching anything upstream.

It also pairs naturally with the pack's Boolean AND / OR operators and its bypass/mute forward nodes. The bypass/mute resolver explicitly walks upstream through the pack's own boolean nodes, so a flipped value feeding a Forward/Bypass on Boolean resolves exactly as you'd expect - this isn't a case where the inverter gets lost in the chain. Chain a couple of flips and an AND and you've got real boolean logic driving your branches.

Input and output

• boolean (default false) - the value to flip.
• Output boolean - its negation.

That's the whole interface. It's deliberately boring.

Install

Part of the vsLinx pack. ComfyUI Manager → search "ComfyUI vsLinx Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/vslinx/ComfyUI-vslinx-nodes.git comfyui-vslinx-nodes

Restart, find it under vsLinx/boolean. No extra dependencies.

The honest take

You could live without this node - you could wire your condition around, or set your widgets backwards, and forget it. But inverted guards come up constantly once you start automating branches, and a single visible inverter is much easier to read than a widget set to the "wrong" polarity with a comment explaining why. It's part of the small set of boolean tools (AND, OR, Flip) that make the pack's bypass/mute nodes express real conditions instead of just single switches. Grab it with the rest of the set, use it when a condition arrives upside-down, and don't overthink it.