Set Float

CFG, denoise strength, LoRA weights, seed upscalers - half the numbers that actually matter in a ComfyUI workflow are floats, and they're usually typed into the same few widgets over and over. Set Float is WorkflowX's answer for that exact crowd: publish one decimal value under a name, read it back anywhere through Get Float, and stop editing six widgets every time you want to test CFG 4 instead of 7.

Like the rest of the Set family, it has no output. That's the point, and it's also the thing that trips people up on first sight. Set Float doesn't pass anything along - it registers value under key in the workflow's config state, and a matching Get Float resolves it downstream. The "Set" nodes publish, the "Get" nodes deliver. You wire the Get, not the Set.

The trick that makes it worth installing

A plain PrimitiveFloat already gives you one source fanned out to many consumers. Set Float's real feature is that its value is config-scoped. WorkflowX's Config SelectorX assigns native ComfyUI groups to named configurations, and Set/Get resolution follows those groups. So you can build one graph where a "Fast" config publishes CFG 3 and a "Quality" config publishes CFG 7 under the same key, then flip between them from a single control. That's the whole workflow-profile pattern WorkflowX is built around - no cloning graphs, no hunting for the node that holds the number.

The inputs are minimal:

• key (STRING) - the name you'll match in Get Float. Empty keys raise an error.
• value (FLOAT, step 0.01) - the number. The small step keeps you honest if you're dragging on the widget.

Install

One install covers every node in the pack:

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

or search WorkflowX Configurator in ComfyUI Manager. Restart ComfyUI, hard-refresh the browser, and you're done - no pip packages, no model downloads. This is plumbing, not inference.

The failure modes worth knowing

• Key mismatch. Get Float looks up the exact key string. "cfg" and "CFG" are different keys.
• Nothing in scope. If the Set Float isn't in the active config's group (or its group is muted/bypassed), Get Float has nothing to resolve and errors out. Match the keys, check the group.
• Expecting a passthrough. There is no output on Set Float. If you wired a chain through it and nothing shows up, that's by design - the value travels through the config state, not the wire.

It's a boring node that quietly kills a very common kind of frustration. Set it once, name it well, and let Config SelectorX do the switching.