Get Node (TJ)

Get Node (TJ) is the receiver half of the pack's wireless routing system, and it's the node to reach for when a wire from one end of a big workflow to the other is making your canvas unreadable. A Set Node (TJ) publishes a value under a name; this node subscribes to that name and hands it over as its value output. No visible connection between the two - the link exists, it's just hidden. The pack's whole pitch is "short wires inside sections, wireless routing between sections," and this is the between-sections part.

How it works

get_name is a dropdown that lists the providers currently registered on the canvas (from Set Nodes and every TJ node with an auto-set provider). Pick one and the node receives whatever that provider emits - the system is reload-safe, so on workflow reload it reconnects to the same provider by name, and it's hover-aware: mouse over the Get node and the pack can show you the hidden wire it's actually tied to.

The wire input is optional and a bit of a cheat code: it's an ANY-typed fallback. If you connect something directly to it, that value is what flows through when no named provider is set. So the node can double as a plain pass-through when you're prototyping and haven't set up names yet.

Outputs: a single value output, typed ANY - it carries whatever the provider sent, IMAGE, STRING, LATENT, anything.

Why you'd bother

The anti-pattern the pack is explicitly fighting is the "giant wire across the whole canvas" workflow. When a workflow grows past a few dozen nodes, one value (a reference image, a seed, a prompt block) often needs to reach five different places. Wire it five times and you've built spaghetti; publish it once from a Set and let each consumer add its own small Get node instead. This is the same ergonomics idea as rgthree's Context/Context Big in the wider ecosystem - bundle the data, keep the graph legible - except TJ does it by name over a registry rather than over a physical wire.

Inputs and outputs that matter

• get_name - the provider to subscribe to. This is the one you'll actually set.
• wire - optional direct fallback.
• value - the received value, any type.

Install

ComfyUI Manager → Install Custom Nodes → search TJ_NODE, or:

cd ComfyUI/custom_nodes
git clone https://github.com/designloves2/ComfyUI-TJ_NODE

Restart ComfyUI. No models or dependencies. Category: ✨ TJ_Node/Wireless.

Gotchas worth knowing

• Duplicate provider names break reconnects. The pack's own docs call this out: two providers named the same thing cause reconnect instability. Name things like a routing map (MAIN_IMAGE, UPSCALE_RESULT), not test.
• If a provider isn't showing up in the dropdown, use the right-click → TJ Node → Refresh ALL Get Nodes menu item to rebuild the provider list.
• This is not a network node - everything is same-canvas. It just hides the wire. If you expected actual IPC between processes, that's the separate Send/Send Point bridge, which works differently.

Get Node is unremarkable on its own - a value in, a value out, nothing computed. Where it shines is the graph it lets you build: dozens of modules, each self-contained, none of them drowning in cables. If your workflows are small, skip it. If they're big enough that you squint at your own canvas, this is the tool that makes the pack worth having.