ComfyDeploy API Int Parameters (Soze)

Same job as ComfyDeploy API String Parameters, swapped to whole numbers: up to five name/value pairs where the value is an integer, packed into the api_parameters string that ComfyDeploy API Node needs to fire a run. If your deployed workflow takes things like a step count, a batch size, or a width in pixels as an input, this is the builder for it.

It's one of five type-specific parameter builders in this pack, alongside String Parameters, Float Parameters, Image Parameters, and the combined Mixed Parameters nodes. Splitting by type keeps each node's widgets honest - an INT widget that actually enforces whole numbers, rather than a generic text field you have to remember to type a number into correctly.

How it works

Same pattern as its string sibling. Each name_N names a parameter on your ComfyDeploy deployment, int_value_N supplies the number, and the node serializes whichever pairs you've filled into one STRING output.

The inputs and outputs that matter

• name_1..name_5 (STRING) paired with int_value_1..int_value_5 (INT, floor of -1) - five optional slots, fill only what you need.
• more_parameters (STRING) - merge in another parameter-builder's output, or hand-written JSON, when five isn't enough or you need other types too.
• Output: api_parameters - feeds directly into ComfyDeploy API Node.

Note the widget floor is -1, not 0 - if your deployment's parameter is meant to be a non-negative count (a batch size, a step count), that's on you to enforce; the node itself will happily send -1 through.

How to install it

Same as the rest of the pack. Via ComfyUI Manager: search "Quality of Life Nodes for ComfyUI", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/SozeInc/ComfyUI_Soze.git
pip install -r ComfyUI_Soze/requirements.txt

No API key needed for this node itself - it's local string-building, no network call. CD_API_KEY is needed further downstream by ComfyDeploy API Node.

Common issues & troubleshooting

The remote workflow ignores your value or errors on type. Double-check the parameter on ComfyDeploy's side is actually typed as an integer, not a float or string - feeding an int-packed parameter into a field expecting a different type is a common source of a silent no-op or a 400 from ComfyDeploy's API.

Name mismatch, again the most common failure. name_N must match the ComfyDeploy deployment's input name exactly - copy it from their dashboard rather than typing from memory.

You need floats, not ints. Reach for ComfyDeploy API Float Parameters instead - this node truncates to whole numbers by type, it won't carry decimal precision.

You only need one or two int values, not five. Fine - leave the rest blank. The node only packs the pairs you've actually named into the outgoing payload, so an unused slot doesn't send a stray zero under an empty name.