RedNode Sender

RedNode Subgraph Send is the writing end of the pack's channel system: it puts values on a named channel so a RedNode Grabber inside a subgraph can pull them out - with nothing wired through the boundary by hand. You add rows in the panel, each gets a name, a type and a socket, and whatever you connect comes out on the other side by name. It's the clean replacement for a canvas covered in Get and Set nodes.

The mechanical heart of the pair is worth repeating, because it's what makes them trustworthy: the Send and the Grabber are spliced into ordinary wires just before the graph runs, and by execution time no channel exists at all. ComfyUI computes execution order purely from links, so there's no hidden ordering to get wrong and no race - which is exactly the failure mode that makes most "wireless" systems feel cursed in practice.

How it works

A Sender has a channel input - a plain name (trimmed to 64 chars) - and a panel of rows. Each row is a named value with a type and a socket: value_1 through value_64. Wire whatever you want to pass into the sockets; everything on the same channel groups together, so several Senders can share a channel and a single Grabber lists them all. The publish toggle is the scope control: off (the default), the channel belongs to the subgraph the Sender sits in; on, the channel is offered further out. The default exists because two instances of one subgraph would otherwise both claim the same name - leave it off unless you specifically need to reach outside.

The inputs

• channel - the channel these values go on.
• publish - off = local to this subgraph; on = offered outward too.
• config - panel state, edited on the node.
• value_1 … value_64 - the values to put on the channel, each wired in the panel.

This is an output node, so it always runs when reached. There are no outputs - its job is complete once the values land on the channel.

Installing it

git clone https://github.com/RedNodeAI/ComfyUI-RedNodeStudio.git ComfyUI/custom_nodes/ComfyUI-RedNodeStudio

Restart ComfyUI, or search RedNode Studio in ComfyUI Manager. No pip deps, no models. Python 3.10+.

The honest notes

The pack calls Sender/Grabber a prototype, and you should treat it that way - the splice logic is straightforward, but it's not the battle-tested core of the pack. The two failure modes to know: channel names must match exactly between ends (a stray space is a silent empty Grabber), and if a value never appears on the Grabber's list, check the Sender's sockets are actually wired - an unconnected row sends nothing. For crossing a subgraph boundary with several values, it's cleaner than a wall of Get/Set nodes, and because the pair becomes real wires before execution, it won't bite you with ordering bugs. Just don't build a mission-critical rig on a prototype label without a fallback plan.