Get Boolean

Booleans are where a lot of "profiles" actually live. Do we run the detailer pass? Is the upscaler on? Does this config use the refiner at all? Those are yes/no decisions, and Get Boolean is the read side of WorkflowX's key/value system for them - paired with Set Boolean, and resolved per config profile at queue time.

It's the smallest of the typed Get family, but don't underestimate it. A boolean wire feeding the "enabled" input on a detailer or a bypass toggle is often the cleanest way to express what a profile is, because it lets the same graph be genuinely different without duplicating anything.

How it works

Identical to its siblings. Set Boolean publishes a value under a key inside a ComfyUI group; Get Boolean, placed wherever the decision is consumed, resolves the key against the selected config. A Config SelectorX controller marks groups Active/Bypass/Mute/Ignore per profile; Get Boolean returns the value from a Set Boolean in an Active group, and the winner among several matches is the highest canvas id (with a warning).

Like every Get node in the pack, it reads the workflow JSON at queue time, uses a digest to skip redundant re-resolution, and exposes the resolved_value, resolved_config, and resolved_digest widgets as frontend-managed provenance. Treat those as read-only - hand-editing them is how you get stale values that refuse to update.

Inputs and outputs

• key (STRING) - exact match against the Set Boolean key.
• resolved_value / resolved_config / resolved_digest (STRING) - internal, UI-managed.
• Output: boolean (BOOLEAN) - a proper boolean socket for enable/disable-style inputs.

One subtlety worth knowing: the value is coerced through a string check ("1", "true", "yes", "on" count as true), so it tolerates being fed a textual value - but you'll normally be picking a true/false toggle on the Set side anyway.

Install

Ships in the WorkflowX-Configurator pack. ComfyUI Manager → search WorkflowX Configurator, or:

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

Restart, hard-refresh the browser. The pack installs no extra Python dependencies.

Common issues

• "No Boolean value found for key 'x'." - no matching Set Boolean in an Active group. Keys are exact and the group must not be muted for the selected profile.
• The toggle never does anything. Confirm the node you're wiring into actually reads a wired boolean - many ComfyUI toggles are widgets, and widgets don't accept wires unless converted to inputs.
• Stale after switching. Re-queue; resolution is at queue time, and the digest cache means a refresh isn't needed - but a re-run is.

Reasonable expectations: this is a young, small pack, so it's a convenience layer more than a community standard. Start with one or two boolean profiles and see if the pattern holds for you before going all-in.