ComfyDeploy API Image Parameters (Soze)

The odd one out in the parameter-builder family: instead of typing values into a widget, you wire up to five actual images from your local graph, and this node turns them into named parameters a remote ComfyDeploy deployment can receive. Useful when the workflow you've deployed needs a reference image, a mask, a starting frame - anything image-typed - as an input.

How it works

Same name/value pairing as the rest of the family - name_N labels the parameter, image_value_N is the image tensor - but unlike the string/int/float builders, an image can't just be dropped into a JSON string. Per the pack's own configuration table, image-parameter upload goes through Azure Blob Storage: the node uploads each connected image to your configured Azure container and gets back a URL, then embeds that URL into the api_parameters payload under the name you gave it. Your deployed ComfyDeploy workflow then loads the image from that URL on its end.

The inputs and outputs that matter

• name_1..name_5 (STRING) with image_value_1..image_value_5 (IMAGE) - up to five optional image slots.
• more_parameters (STRING) - merge in another parameter node's output for non-image parameters, or extra pairs past five.
• Output: api_parameters - feeds into ComfyDeploy API Node.

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

This node needs two things set in your environment beyond the base install: CD_API_KEY for ComfyDeploy itself, and - specific to this node - SOZE_AZURE_STORAGE_CONNECTION_STRING, since it's the pack's node whose README entry explicitly calls out Azure Blob upload. Both go in your environment or a .env file at the repo root; the README is explicit that this file should never be committed, and to rotate a key you suspect leaked.

Common issues & troubleshooting

Silent failure or an upload error, and everything else looks fine. This is the tell for a missing or wrong SOZE_AZURE_STORAGE_CONNECTION_STRING - it's easy to set CD_API_KEY and forget this one exists, since none of the other ComfyDeploy nodes in this pack need it.

You need an actual Azure Storage account. This isn't optional infrastructure the node spins up for you - you need your own Blob Storage container and its connection string. If you don't already have one, this is the node in the whole pack with the highest setup cost.

The remote workflow can't reach the image. Check your container's access level - if it's private, ComfyDeploy's servers won't be able to fetch the URL this node hands them. It generally needs to be readable without additional auth on ComfyDeploy's end.

Only need strings or numbers? Skip this node entirely - ComfyDeploy API String/Int/Float Parameters don't need Azure at all, only images do.