XPipeGate

Think of an audio mixer: fifty channels, each with its own mute button, and you can kill a channel without unplugging anything. XPipeGate is exactly that, but for the pack's XPipe bundle - one node that gates up to 50 channels of data, each with its own enable switch. It's the missing control surface for workflows that keep hitting "I want to turn this branch off without deleting the wires."

How it works

The node merges two sources of values per channel:

• xpipe_in - an optional incoming XPipe bundle. Its slot values seed the channels, so you can chain gates.
• input_1 … input_50 - optional direct inputs for each channel. A direct input overrides the value that came in via the bundle for that channel.

Each channel has an enable_N switch. Disabled channels output nothing (None) and skip their input entirely. Enabled channels take the direct input if present, else the bundle value, and emit it on the matching output_N port. There's also xpipe_out, which carries all enabled channel values as a fresh bundle - and it's always a valid bundle, even when nothing is connected. That "always valid" guarantee is the reason downstream XPipe nodes never choke on an empty gate.

Two quality-of-life toggles live on the node: type_warning (shows a visual warning when a channel output is wired to an incompatible input type - the classic striped + blinking link treatment) and port_names, a frontend-managed string for naming channels so the panel reads like your actual workflow rather than numbers 1 through 50.

The inputs that matter

For a beginner it's one: the enable_* switches. Everything else is optional - you can drop an XPipeGate into a workflow with nothing connected and it just sits there being a valid empty bundle, which is a much nicer starting point than a node that demands wiring before it'll run. If you're chaining gates, hook xpipe_in from the upstream bundle and use direct inputs to override only the channels you care about.

Installing it

XPipeGate ships in ComfyUI-Xz3r0-Nodes (by Xz3r0-M) under ♾️ Xz3r0/Workflow-Processing. ComfyUI Manager: search ComfyUI-Xz3r0-Nodes and install. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Xz3r0-M/ComfyUI-Xz3r0-Nodes.git
cd ComfyUI-Xz3r0-Nodes
pip install -r requirements.txt

Restart ComfyUI after. No models, no GPU cost - this one's a frontend-heavy gate node, so if the panel looks wrong, update ComfyUI rather than hunting for a config bug.

Gotchas

Two things to keep straight. A disabled channel doesn't just output None from the bundle - it also skips evaluating its direct input (the inputs are lazy), which is a small perf win and means a dead channel can't drag a broken upstream into the run. And remember direct input wins over the bundle on the same channel; if a channel seems stuck on an old value, check whether something is plugged into its input_N that you forgot about.