✈️ CR Module Pipe Loader

The entry point into Comfyroll's biggest pipe pattern: bundle up to nine separate wires - model, positive conditioning, negative conditioning, latent, VAE, CLIP, ControlNet, image, and seed - into one PIPE_LINE wire, and route that single connection through however much of your graph doesn't actually need to touch any of those values individually.

How it works

Every input is optional, which is deliberate: you don't have to fill all nine slots, just the ones your workflow actually uses. Whatever you connect gets packed into the outgoing pipe; leave the rest disconnected and they simply aren't part of the bundle. This is the start of the chain - from here you'd typically route straight to a CR Module Output if something downstream needs to update one field, or to a CR Module Input wherever you need to unpack the bundle and actually use the values.

Comfyroll's own README credits Efficiency Nodes and tinyterra's pipe nodes as the direct inspiration for this pattern, and it's worth naming the comparison honestly: this is the same "bundle everything into one wire so the graph stays readable" idea that rgthree-comfy's Context nodes solve today, just Comfyroll's earlier, SDXL-era take on it. The nine-slot version here is a fixed, purpose-built bundle rather than a general-purpose one - it knows about model/conditioning/latent/vae/clip/controlnet/image/seed specifically because that's what a typical sampling pipeline juggles, not because it's trying to carry arbitrary data.

Inputs and outputs that matter

• Optional: model, pos, neg, latent, vae, clip, controlnet, image, seed - fill in whatever you need.
• Output: pipe (type PIPE_LINE) plus show_help.

How to install it

ComfyUI Manager: search "Comfyroll Studio", install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, restart. Pure plumbing - no models to download for this node itself, though of course whatever model/LoRA/checkpoint you're feeding into it needs to already be where ComfyUI expects it.

Common issues

If you're building a brand-new workflow rather than maintaining an old Comfyroll-based template, it's worth knowing this pattern's mindshare has moved on - reddit mentions of Comfyroll specifically have fallen from roughly a couple dozen a month in early 2024 to around one a month by mid-2026, and rgthree's Context nodes are the version of "bundle the graph" that gets recommended in fresh workflows now. That doesn't make this node broken or wrong - old templates built on it still run exactly as before, class names are stable - it's just not where new adoption is happening.

The functional gotcha: PIPE_LINE only talks to other Comfyroll pipe nodes, so once you commit to building a pipe here, everything downstream that needs to read from it has to be a Comfyroll CR Module Input/Output node too - you can't tap a generic ComfyUI socket mid-pipe. And as with every node in this large pack: if CR Module Pipe Loader doesn't show up in the search menu, check your ComfyUI console for an import error elsewhere in the pack before assuming this specific node is the problem.