Nodes/PromptModels Studio/📤 PRO Get Node
ComfyUI Node

📤 PRO Get Node

Read back any value you stored with PRO Set

By cdanielp·Created 9 months ago·Updated 2 months ago· 28
📤 PRO Get Node
    • star
    namemy_variable

    Set/Get node pairs are the trick ComfyUI workflows use to "remember" a value from one part of the graph and read it in another, without drawing a wire across your whole canvas. PRO_GetNode is the read half of that pair: it reaches into the shared in-memory store the PRO nodes use, pulls out whatever was saved under a variable name, and hands it to you as a wildcard output that plugs into almost anything. If you've seen rgthree's Set/Get nodes, you already know the idea - this is this pack's take on it, sharing the same store.

    What it's for

    The honest use case: a seed you want consistent across runs, a text value computed once and reused in three places, a conditioning you want to stash and reference later without a rat's nest of wires. PRO_SetNode writes into the cache, PRO_GetNode reads it back, and because the store is keyed by name, the two nodes don't need to touch. It also saves workflow history in a way a direct wire doesn't - the value lives on, so you can change it in one spot and every Get picks it up.

    How it works

    PRO_SetNode stores the value under a variable name (derived from the node's name widget or its title, e.g. Set_myvar). PRO_GetNode looks the name up in the same in-memory cache and returns whatever was stored, along with the type it was registered under. The output is a wildcard * type, so it adapts to whatever you stored - model, image, latent, string, you name it. If the name doesn't exist, it raises a ValueError that lists the currently available variable names, which is the fastest possible way to learn you mistyped something.

    The input and output that matter

    • name (STRING, default my_variable) - the only widget. This is the key into the cache. Keep it in sync with your PRO_SetNode's name, or title your Set node Set_whatever and the Get picks it up from the title.
    • * output - type-agnostic. Wire it wherever the stored value's type is accepted.

    One genuinely handy detail: the node re-evaluates every run (IS_CHANGED returns NaN), so it always reflects the latest value in the cache, not a cached stale one.

    Installing it

    It ships in COMFYUI_PROMPTMODELS (PromptModels Studio in Manager). Install the pack, restart:

    cd ComfyUI/custom_nodes
    git clone https://github.com/cdanielp/COMFYUI_PROMPTMODELS
    

    Needs ComfyUI 0.26.0+. No API keys - this is local plumbing.

    Common issues

    The classic failure is the ValueError for a missing variable, which happens when you run a Get before its matching Set ever executed, or you cleared the cache (PRO_ClearCacheNode exists for that). Another gotcha: the cache is per-session memory, so a ComfyUI restart wipes everything - if your Get errors after a restart, re-run the Set node once. Because it's type-wildcard, a genuinely mismatched type will surface downstream rather than here, so when a workflow errors, check that the Set and Get agree on what they're passing around.

    CategoryGetSetNode_Pro/utils

    Inputs (1)

    NameTypeDefaultDescription
    nameoptSTRINGmy_variable

    Outputs (1)

    NameTypeDescription
    star*