ComfyUI Node

SimpleGet

SimpleGet

By jessesep·Created 9 months ago·Updated 2 months ago· 0
SimpleGet
  • trigger
  • value
namevar

SimpleGet is the other half of the SimpleVariables pair. Where SimpleSet stores a value under a name, SimpleGet pulls it back - type a name, and the value appears on the value output, ready to wire into anything. Reference image, seed, prompt, project path, model: if it was Set this session, Get can find it. The node even retitles itself (Get: my_seed) and shows a preview of what it found after each run, so you can see at a glance whether you're pulling the right thing.

This is the node people reach for when they're tired of dragging wires. Community threads on Set/Get nodes in ComfyUI consistently describe the same win: store a value once, and you can reach it from anywhere in a large graph without a cable running across everything. Get is where that payoff lands.

How it works. Same shared in-memory dictionary as SimpleSet. On execution it looks up _variables.get(name) and emits whatever it finds. The lookup is case-sensitive and exact, and the value is whatever type was stored - the value output is a wildcard, so it plugs straight into image inputs, model inputs, string inputs, wherever.

The two inputs.

  • name - the key you're retrieving. Must match the Set exactly, including case.
  • trigger - a wildcard input that doesn't feed the output at all. It exists purely to control when this node runs, and it's the most important thing in the pack to understand.

The execution-order trap. This is where every SimpleVariables user gets burned at least once. ComfyUI runs nodes in dependency order. If there's no wire between your SimpleSet and your SimpleGet, ComfyUI has no reason to run Set first - Get can execute before Set, look up a name that doesn't exist yet, and hand you None. Both nodes deliberately always re-run (their IS_CHANGED returns the current time), so it's not a caching problem; it's purely ordering.

The fix is the trigger input. Wire your SimpleSet's output into the Get's trigger, and ComfyUI now knows Get depends on Set and will run Set first. If you're getting NOT SET in the preview when you're sure you set the variable, this is the cause - check your trigger wire before anything else.

Missing names return None, not an error. If the name was never set (or was cleared), Get quietly outputs None and shows name = NOT SET on the node. Nothing crashes; your downstream node just receives a silent None, which can make the failure hard to spot. If you've been debugging for an hour, read the preview text.

Also keep in mind: it only finds variables from the current session. Restart ComfyUI and everything's gone - the dictionary lives in memory only, so there's no state to carry over between sessions.

Install. Same as every node in the pack - no dependencies, no model downloads.

cd ComfyUI/custom_nodes
git clone https://github.com/jessesep/SimpleVariables.git

Restart ComfyUI, search "variable", drop a Get next to whatever needs the value. Pair it with a Set, wire the trigger, and you've got a named value you can reuse across a graph that stays readable.

CategorySimpleVariables

Inputs (2)

NameTypeDefaultDescription
nameSTRINGvar
triggeropt*

Outputs (1)

NameTypeDescription
value*