ComfyDeploy API Float Parameters (Soze)

The decimal-number version of the same parameter-builder pattern: up to five name/value pairs, values as floats this time, packed into the api_parameters string ComfyDeploy API Node needs. Reach for this one when your deployed workflow takes something like a CFG scale, a denoise strength, or a LoRA weight as an input - anything where "3" and "3.0" genuinely aren't the same request.

This whole family of nodes exists because ComfyDeploy's queue API wants a single structured payload, not five separate widgets scattered across your graph. Rather than making every parameter-type node also handle every other type, the pack splits by type and gives you more_parameters to stitch them back together - a small, deliberate tradeoff: more nodes to wire for a mixed call, but each individual node stays simple and its widget types stay honest (a float widget that's actually a float widget, not a text box you're trusting yourself to type numbers into).

How it works

Identical mechanism to its string and int siblings - name_N labels the parameter, number_value_N carries the float value, and whatever pairs you've filled get serialized into one STRING. Only the pairs you've actually named get included in the payload; leaving name_3 blank while filling name_1 and name_2 sends just those two, not three empty entries.

The inputs and outputs that matter

• name_1..name_5 (STRING) with number_value_1..number_value_5 (FLOAT, default 0) - five optional pairs.
• more_parameters - merge in output from another parameter node, or raw JSON, to go past five slots or mix in other types.
• Output: api_parameters, wired to ComfyDeploy API Node.

How to install it

Via ComfyUI Manager, search "Quality of Life Nodes for ComfyUI"; or by hand:

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

restart ComfyUI. No API key for this node itself; CD_API_KEY is what ComfyDeploy API Node needs downstream.

Common issues & troubleshooting

Precision looks off. If the remote deployment rounds or truncates a value you sent, that's happening on ComfyDeploy's side (their input's declared type), not in this node - this node passes the float through as-is.

Name mismatch. Same rule as every parameter node in this family: name_N has to be the exact input name your ComfyDeploy deployment expects.

You've got a mix of types to send. Chain this into more_parameters on one of the Mixed Parameters nodes, or vice versa, rather than juggling four separate parameter builders for one deployment call.

You only need one or two float values. Five slots is the ceiling, not a requirement - a single filled pair works exactly the same as all five filled. Don't feel obligated to pad the node out.