Set Int

If you've ever had the same seed, step count, or batch size typed into four different nodes and edited all four by hand, Set Int is aimed directly at you. It's the "publish" half of WorkflowX's keyed value system: you give a number a name, and anywhere in your workflow that wants that number grabs it through the matching Get Int node. Change it once, and every consumer updates.

The name is accurate but the node is easy to misread at first glance because it has no output. Nothing comes out of Set Int. It doesn't need to - its job is to register value under key in WorkflowX's config state so a Get Int with the same key can resolve it later. That's the whole mechanism, and it's the same one the whole Get Set Go family (Set Float, Set String, Set Boolean, Set Sampler…) uses.

Why it's more than a glorified Primitive

ComfyUI already ships PrimitiveInt, so why bother? The difference is that Set Int's value is resolved per configuration. WorkflowX's Config SelectorX lets you assign ComfyUI native groups to named configurations, and the Set/Get pair respects that scoping. So you can have one workflow with a "Draft" group publishing steps=20 and a "Final" group publishing steps=40 under the same key, flip Config SelectorX, and every Get Int downstream picks up the new number without touching the graph. That's the workflow-profile pattern from the pack's own example - one graph, several named configurations, instead of cloning the whole thing three times.

The two inputs are all there is:

• key (STRING) - the name of the value. Keep it unique and readable; empty keys are rejected outright.
• value (INT, −2,147,483,648 to 2,147,483,647) - the number itself.

Installing and wiring it

Install the whole pack once via ComfyUI Manager (search WorkflowX Configurator) or:

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

Restart ComfyUI and refresh the browser. There are no pip dependencies to chase and no model files - this is pure graph plumbing.

Wire a Get Int node with the same key where you want the value, and convert the downstream widget to an input if needed. The practical pattern: put Set Int inside a native group, assign that group to a config in Config SelectorX, and give different configs different values.

Where people get burned

• Empty key. The node raises Set Int key cannot be empty. - the key is mandatory, not cosmetic.
• Get with nothing to resolve. If no Set Int with that key is in the active config's scope, the Get errors out. Either the key names don't match (case matters) or the Set is sitting in a group that's bypassed or muted for the current config.
• Thinking it switches on its own. The value only changes when Config SelectorX changes the active config. A lone Set Int with no config involvement behaves like a plain value holder - fine, but then a Primitive would've been simpler.

It's a small node, but it's the keystone of WorkflowX's whole "one workflow, many profiles" pitch. Start with one keyed value and you'll see the appeal of the pattern quickly.