Nodes/Mithril-Nodes for ComfyUI/Ⓜ️ Get Multiplexer Gateway
ComfyUI Node

Ⓜ️ Get Multiplexer Gateway

Get Multiplexer Gateway reads what Set wrote

By MithrilMan·Created about a year ago·Updated about a year ago· 0
Ⓜ️ Get Multiplexer Gateway
    • *
    gateway_name

    Get Multiplexer Gateway is the other half of MithrilNodes' named-data trick. Where Set Multiplexer Gateway stashes a value under a name, this node pulls it back out by that name - think of it as a distant relay: the data leaves the stage at one point in your graph and reappears wherever you drop a Get node. Same value, no long ugly wire dragging across the canvas.

    The node is genuinely pleasant to use because of its design-time dropdown: gateway_name isn't a typed string, it's a dropdown that the pack's frontend populates by scanning your graph for every Set Multiplexer Gateway and listing their names. You don't remember spellings, you just pick. The output is typed *, so whatever the Set stored - model, conditioning, string, latent - comes out ready to plug into whatever needs it.

    What you'll actually touch

    • gateway_name - the dropdown. If it only shows N/A, that's the sentinel for "no Set nodes found," and it tells you something important (below).
    • output - the retrieved value, any type, routed straight from the matching Set node's data.

    The gotchas, and they're real ones

    1. The dropdown is graph-scanned, so it's only as good as the Set nodes present. If you load a workflow from JSON and the frontend hasn't run its scan, you'll see only N/A. Add a Set node, or re-open the workflow, and the choices should populate.
    2. Execution order is not your friend. The data lives in a process-global store, filled at runtime when the matching Set node executes. Run the Get before the Set in the queue and you get a hard error: "Gateway not found or has not been executed yet." In practice that means the Set must be upstream of (or at least scheduled before) the Get - which, with dependency-based execution, usually means making the Set's branch actually feed into whatever the Get's output is used by. That's the fiddliest part of this feature, and it catches people regularly.
    3. The store doesn't persist. Restart ComfyUI, and everything named in the previous session is gone until the Set nodes run again. This is a same-run tool, not a settings system.

    Install

    Part of MithrilNodes: ComfyUI Manager → Install Custom Nodes → search Mithril ("Mithril-Nodes for ComfyUI"), or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/MithrilMan/ComfyUI-MithrilNodes
    

    Restart after. No requirements, no model downloads. The pack is at 0.1.0 with a placeholder README, so go in knowing this is a fresh project - the gateways work, but if you need a mature named-routing system with more battle-testing, rgthree's Context nodes remain the safer default.

    CategoryⓂ️ MithrilNodes/Gateways

    Inputs (1)

    NameTypeDefaultDescription
    gateway_nameCOMBO1 options: N/A

    Outputs (1)

    NameTypeDescription
    **