Set Boolean

On/off. Enabled/disabled. Use hires fix, don't use hires fix. Booleans are the most boring and most repeated value in any workflow, which makes them the perfect thing to centralize. Set Boolean publishes a true/false value under a named key, and Get Boolean reads it back wherever the graph needs to know the answer. Flip one widget, and every node that asks "should I?" agrees on the answer.

Like the whole Set family, it has no output. Set Boolean writes value under key into WorkflowX's config state; the matching Get Boolean resolves it. There's no passthrough - if you wanted the value to also travel on a wire, Set Relay is the one with an output.

The part that's actually clever

A toggle you can flip is nice; a toggle that changes by configuration is the workflow trick. WorkflowX's Config SelectorX scopes Set/Get resolution to native ComfyUI groups, so a "Fast" config can publish hires_fix=false and a "Quality" config can publish hires_fix=true under the same key. One graph, one switch that follows whichever config is active, and the whole "Fast / Quality / Experimental" profile idea works without duplicating anything.

That's the workflow-profile pattern the pack advertises, and booleans are a natural first test of it because they're everywhere: enable/disable a LoRA row, toggle a detailer branch, gate a color-match step.

The inputs:

• key (STRING) - the name. Empty keys are rejected.
• value (BOOLEAN) - the toggle itself, default false.

Install

The pack is one install for all its nodes:

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

or search WorkflowX Configurator in ComfyUI Manager, then restart ComfyUI and hard-refresh the browser. No pip dependencies, no model files.

Wire a Get Boolean with the same key into a converted boolean input downstream, and place the Set inside a group you've assigned to a config in Config SelectorX if you want per-config values.

Gotchas that actually bite

• Empty key = hard error. Set Boolean key cannot be empty. - the key is mandatory.
• Mismatched keys. hires vs hires_fix won't resolve, and a Get Boolean with nothing to resolve errors out rather than defaulting to false. That's intentional: a silent default-false would quietly disable a branch you thought was active.
• Don't reach for it for routing. If you want to choose between two inputs, that's a switch node (rgthree's Any Switch or similar), not a Set/Get pair. Set/Get is about publishing a value, not routing data.

A one-widget node that earns its place the moment you're juggling more than one configuration of the same workflow.