Set Sampler

Every KSampler in your workflow asks for a sampler name, and if you've got three samplers chained - base, hires, detailer - you're choosing euler vs dpmpp_2m_sde in three different dropdowns. Set Sampler is WorkflowX's way of centralizing that choice: you pick the sampler once under a named key, and Get Sampler feeds it to every sampler node that needs it. Change one dropdown, the whole graph agrees.

No output, same as its Set siblings. Set Sampler registers the chosen sampler under key in WorkflowX's config state; the matching Get Sampler resolves it. And because it's a full dropdown validated against your running ComfyUI install (44 sampler options in the schema, everything from euler to euler_ancestral_cfg_pp to dpm_fast), you get the real ComfyUI sampler list, not a hardcoded snapshot - if your install adds samplers, they show up.

Why it beats typing the name in everywhere

The obvious win is one source of truth: switch euler → dpmpp_2m_sde once, and every sampler downstream follows. The deeper win is config scoping, which is the whole point of WorkflowX's design. Config SelectorX assigns native groups to named configurations, so a "Fast" config can publish euler_ancestral while a "Quality" config publishes dpmpp_2m_sde under the same key - one graph, sampler choice following whichever config is active. That's the workflow-profile pattern the pack is built around, and sampler is one of the most natural values for it because it's a single dropdown you're always second-guessing.

Inputs:

• key (STRING) - the lookup name. Empty keys are rejected.
• value - the sampler dropdown, validated against the installed ComfyUI.

Install

One pack, one install:

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. No pip deps, no model downloads.

Wire a Get Sampler with the same key into a KSampler's converted sampler_name input, and it becomes the single authority for that slot.

The practical gotchas

• Key discipline matters. The sampler dropdown has no default text - an empty or mistyped key leaves Get Sampler unable to resolve, and it errors rather than guessing.
• Pair type matters. Get Sampler only resolves Set Sampler values; a Set Scheduler won't satisfy it. The two are separate keyed channels because they feed different widgets.
• It validates, but it won't rescue a bad combo. The dropdown only lists what your ComfyUI actually supports, which removes the classic "I typed a sampler that doesn't exist" failure. It can't tell you a sampler is a bad choice for your checkpoint - that part is still on you, and if you're on a modern guidance-distilled model you want the sampler that ships with it, not muscle memory from SDXL days.

Quiet, centralizing, and genuinely useful once your workflow has more than one sampler.