ComfyDeploy API String Parameters (Soze)

Before you can fire a job at ComfyDeploy with ComfyDeploy API Node, something has to build the parameters it sends. This is that node - for string-typed parameters specifically. Up to five name/value string pairs go in, one packed api_parameters string comes out, ready to hand to the node that actually queues the run.

How it works

Each pair is a name_N / string_value_N widget: name_N is the parameter's name - and it has to match, exactly, whatever input name your deployed ComfyDeploy workflow was set up to expect (whatever you called it when you defined that workflow's external inputs on ComfyDeploy). string_value_N is what gets sent for it. The node packs the pairs you've filled in into the format the ComfyDeploy queue API wants and outputs it as a single STRING.

The inputs and outputs that matter

• name_1..name_5 and string_value_1..string_value_5 - five optional name/value slots. Leave any pair blank (default is empty string for both) if you don't need it; you don't have to fill all five.
• more_parameters (STRING, default empty) - an escape hatch. If your deployment needs more than five string parameters, or a mix of types, wire the output of another parameter-builder node into this field to merge them together - or hand-write extra JSON here if you know the shape ComfyDeploy expects.
• Output: api_parameters - one STRING, wired straight into ComfyDeploy API Node's api_parameters input.

If your deployment needs a genuine mix of strings, numbers, booleans and images rather than five strings, look at ComfyDeploy API Mixed Parameters (or the V2 revision) instead - it does all of that in one node rather than chaining several together.

How to install it

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

then restart. This particular node doesn't need any API key itself - it's pure string packing, no network call - but it's useless without ComfyDeploy API Node downstream, which does need CD_API_KEY set.

Common issues & troubleshooting

Your deployed workflow doesn't receive the value. This is almost always a name mismatch - name_N has to be character-for-character what your ComfyDeploy deployment's input is called. Go check the deployment's input list on ComfyDeploy's own dashboard rather than guessing from your local workflow's node titles.

You need more than five parameters. Chain a second parameter-builder node into more_parameters rather than trying to cram extra pairs into one node - the node only has five slots by design.

Mixing types is awkward with this node alone. That's expected - this one is strings-only. Reach for Int Parameters, Float Parameters, Image Parameters, or one of the Mixed Parameters nodes for other types, and merge them through more_parameters.