Set Reference

Reference images are the most fiddly thing to route in a workflow - you've got a face reference feeding IPAdapter, a style reference feeding another branch, and every one is a thick IMAGE wire you have to drag across the whole graph. Set Reference is WorkflowX's routing node for exactly this: it takes any connected object (images, audio, video, whatever), publishes it under a key, and lets Get Reference nodes pull it out anywhere. The same keyed, config-aware routing as Set Relay, with one extra trick - per-node muting.

It has an output. value passes straight through, so the reference stays usable on the local path while also being published. And its mute input is where it gets interesting: when mute is true, every Get Reference sharing that key is omitted from the API prompt using ComfyUI's native mute semantics - the whole branch silently stops running without you cutting a single wire.

The mute model deserves a careful read, because it's backwards from what you might expect:

• Set Reference's mute is a master switch for its key. Mute the Set, and all matching Gets are omitted. The Set's own output still works directly in either state.
• Each Get Reference has its own independent mute. Muting one Get doesn't affect its siblings, and it works exactly like manually muting that node.

That gives you "kill all consumers of this reference" from one place, or "kill just this one consumer" from another - both without touching the graph structure.

Inputs and outputs

• key (STRING) - the lookup name; empty keys are rejected.
• value (*) - the reference object, any type.
• mute (BOOLEAN, default false) - the master mute for this key's Gets.

Output: value (*), passed through unchanged.

Install

The whole pack is one install:

cd ComfyUI/custom_nodes
git clone https://github.com/haroonaslam/WorkflowX-Configurator

or search WorkflowX Configurator in ComfyUI Manager, restart ComfyUI, refresh the browser. No pip deps, no model downloads.

Where people get confused

• Mute is per-key on the Set, per-node on the Get. Set mute off + one Get muted = that one Get drops, its siblings still run. Set mute on = every matching Get drops. Neither state affects the Set's own passthrough output.
• Wildcard socket, your responsibility. * accepts anything, so nothing type-checks your wiring. Keep keys descriptive.
• It's a relay, not a typed Set. Get Reference resolves Set Reference values only - a Set Relay on the same key won't satisfy it.

The most workflow-shaped node in the family: route your reference, then control its participation without rewiring. Great for "here's the shot, now which branches should see it" setups.