Group Configurator

Deprecated, but this one actually did the interesting work. Group Configurator is where the old WorkflowX config system stored the meat: a mapping of ComfyUI group names to Active, Bypass, or Mute modes for a single named config. One Group Configurator per profile, a Config Selector pointing at the active profile, and the pack's Get nodes could resolve values from whichever group was Active.

The pack's README is unambiguous: the four legacy configurator nodes - Group Configurator included - remain registered only so old workflows load. New workflows use Config SelectorX, which folds this whole job into its Configs editor.

How it works

Group Configurator takes a config_name and a config_json mapping group names to modes. The config_json is frontend-managed - the browser extension writes {"Faster Config": "Active", "Real Config": "Mute", "Speedup Lora": "Bypass"} style objects for you. The node validates the JSON when it runs (values must be Active/Bypass/Mute/Ignore) but applies nothing itself.

The application happens elsewhere, at queue time. The resolution machinery scans the workflow JSON, finds Group Configurator nodes whose config_name matches the active selected_config from a Config Selector node, reads the group modes, and - using the physical positions of nodes inside groups - lets each Get node resolve its value from a Set node that sits in an Active group. It's geometric and a little clever: a node is "in" a group when its bounding box intersects the group's, which is why this design could break if you dragged nodes across group boundaries without noticing.

Inputs

• config_name (STRING) - the profile this mapping belongs to.
• config_json (STRING) - frontend-managed group→mode mapping. Read-only for you.

Migrating off it

Load the old workflow, note which groups each config marks Active/Bypass/Mute, add a Config SelectorX, recreate those modes in its Configs editor (and the scope assignments in Scopes), verify every Get/Relay still resolves, then delete the legacy nodes and save under a new filename.

Install

In WorkflowX-Configurator - Manager search WorkflowX Configurator, or clone https://github.com/haroonaslam/WorkflowX-Configurator into ComfyUI/custom_nodes, restart, hard-refresh.

Common issues

• "config_json contains invalid mode" - a hand-edited value isn't one of Active/Bypass/Mute/Ignore. Reset through the UI.
• Groups stopped affecting resolution after I moved nodes. That's the geometric containment biting - a node's membership is decided by rectangle overlap with the group. Config SelectorX's scopes don't have this failure mode, another reason to migrate.
• Config name doesn't match. The Group Configurator's config_name must equal the Config Selector's selected_config exactly.

This node is a good illustration of why the author moved to a unified controller: the old chain (Selector + Group Configurator + Group Scopes) spread the config logic across three nodes, each validating its own slice of state. Config SelectorX keeps all of it in one place. Appreciate the idea, migrate the workflow.