Pyobjects/Global Var Get

This is the read half of LogicUtils' in-memory key-value store. Something else in your graph - most likely GlobalVarSetIfNotExistsNode, or the pack's plain set node - wrote a value under a name. This node hands that value back, given the same name. It's the same "teleport a value across the canvas" trick you'll recognize from rgthree's get/set nodes or Anything Everywhere: instead of dragging one long wire across a sprawling workflow, you stash a value once and pull it out wherever you actually need it.

How it works

You give it a key, it looks that key up in a shared dictionary living in the running ComfyUI process, and returns whatever's stored there on the flexible * output - could be a string, a number, an image, anything. Because it's marked as an output node, it's allowed to sit at the end of a chain with nothing wired past it and still execute when you queue - handy if you just want to peek at a stored value rather than route it anywhere.

The optional trigger input is there purely for execution ordering, not data. ComfyUI doesn't guarantee that a value gets set before it gets read just because the set node is somewhere on the canvas - wiring anything into trigger forces this node to wait until whatever feeds it has actually run first. If you're not seeing the value you expect, this is usually why: the get executed before the matching set did.

Inputs and outputs

• key (default my_key) - must match exactly what the corresponding set node used. Typos here are the number one cause of "why is this empty."
• trigger (optional, *) - wire anything in just to force run order; the value itself is ignored.

Output is the stored value on the wildcard * slot.

Installing ComfyUI-LogicUtils

ComfyUI Manager: Install Custom Nodes → search "ComfyUI-LogicUtils" → install → restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/aria1th/ComfyUI-LogicUtils

Restart ComfyUI. No dependencies.

Worth knowing

The store this reads from lives only in the running process - restart ComfyUI and it's gone, unlike GlobalVarSaveNode/GlobalVarLoadNode, which write the same kind of value out to an actual JSON file on disk. Keep your keys distinctive: reuse my_key in two different spots of a large workflow (or across two workflows sharing the same server) and they'll silently stomp on each other. This is part of aria1th's (AngelBottomless's) LogicUtils grab-bag of utility nodes - barely documented by the README's own admission, and quiet since public commits stopped in January 2026 - so there's no changelog or FAQ to lean on if the ordering behavior surprises you; the trigger input is the fix, use it liberally.