ComfyUI Node

Get Int

One key, many configs — stop retyping steps and CFG for every profile

By haroonaslam·Created 4 months ago·Updated 7 days ago· 10
Get Int
    • int
    key
    resolved_value
    resolved_config
    resolved_digest

    The classic ComfyUI primitive problem: you have one workflow and three moods. Fast runs want 4 steps, quality runs want 24, and every time you switch you're clicking into the KSampler, clearing the box, typing a new number. Get Int is the read side of WorkflowX's answer to that. You publish a value once with a Set Int node, then Get Int fetches it at queue time - and which Set Int wins depends on the config profile you've selected.

    It's the same idea as core ComfyUI's PrimitiveInt fanned out to several consumers, except the value isn't fixed. The one wire feeding your sampler's steps, CFG, or seed input becomes a slot that a named config fills differently. That's the whole trick of this pack, and it's a genuinely nicer way to run a multi-profile workflow than cloning the graph once per setting.

    How it works

    Set Int and Get Int talk by key, a plain string, and both nodes physically live inside ComfyUI groups on your canvas. A controller node - the modern Config SelectorX - marks each group as Active, Bypass, Mute, or Ignore per config profile. At queue time Get Int reads the workflow JSON, hunts for Set Int nodes whose key matches, keeps only the ones sitting inside groups that are Active for the selected config, and returns that value. If several still match, the last one on the canvas wins (with a console warning), so keep keys unique inside a scope.

    Two implementation details are worth knowing because they explain the node's behavior. First, the resolved_value, resolved_config, and resolved_digest fields you see are UI-managed cache and provenance - a fingerprint of what was resolved. Leave them alone; the node re-resolves live whenever the digest doesn't match, which is why switching configs works without a browser refresh. Second, resolution happens before queueing, not during sampling, so there's no per-run overhead to speak of.

    Inputs and outputs

    The only thing you really set is key - the exact string the Set Int node uses. Everything else is internal.

    • key (STRING) - must match a Set Int key character-for-character.
    • resolved_value / resolved_config / resolved_digest (STRING) - managed by the frontend; don't hand-edit.
    • Output: int (INT) - wire into any integer input that accepts a wire, like steps, CFG, or seed.

    Install

    It ships in the WorkflowX-Configurator pack. Install via ComfyUI Manager by searching WorkflowX Configurator, or:

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

    Restart ComfyUI and hard-refresh the browser tab. The pack has no Python dependencies beyond what ComfyUI already ships, so there's nothing extra to pip install.

    Common issues

    • "No Int value found for key 'x'." - there's no matching Set Int in an Active group. Check the key is spelled identically on both nodes and that the group the Set sits in isn't Muted or Ignored in the current config.
    • Wrong value resolves. Two Set Ints share a key in Active groups; rename one or scope them into different groups.
    • Type mismatch. A Get Int won't pick up a Set String. The typed families are strict, and that's deliberate - Set/Get types must match is the pack's own contract.

    One honest caveat: this pack is young and small (a couple of r/comfyui release posts, modest engagement). For a single-profile workflow, a plain primitive is simpler. Get Int pays off the moment you're maintaining two or more named profiles in one graph.

    CategoryWorkflowX/Get Set Go

    Inputs (4)

    NameTypeDefaultDescription
    keySTRING
    resolved_valueSTRING
    resolved_configSTRING
    resolved_digestSTRING

    Outputs (1)

    NameTypeDescription
    intINT