ComfyUI Client Set Int (Yogurt Nodes)

The remote workflow you loaded into ComfyUI Client Load is a template with hardcoded values. This node is how you change the integer ones. ComfyUI Client Set Int takes your COMFYUI_CLIENT handle, targets a node by id or title, names an input field, and writes a new integer into it - then passes the client onward, patched and ready.

What it's for

Think of the workflow JSON as a form and these Set nodes as the fields you fill before hitting submit. Set Int handles the steps, cfg, batch_size, width/height, clip_skip-style inputs on the remote graph. The neat part is that the value can come from anywhere in your local graph - an Int node, a logic node's output, a slider driven by something else. So you can compute a value locally (say, steps scaled to your image resolution) and inject it into a remote workflow that never knew the calculation existed. That's the whole point of the family: keep the brain local, send the job remote.

The Set nodes are chainable - Set Int, then Set Float, then Set Seed, each taking the client from the previous one and handing it to the next, until Run finally submits the fully-patched workflow.

Inputs

• client - the handle from Load or a previous Set node.
• node - the node id or title in the remote workflow whose input you're targeting. Same stability rule as the rest of the family: titles survive renumbering better than ids.
• key - the input field name, exactly as it appears in the workflow JSON. steps, cfg, whatever the remote node calls it. Misspell it and the patch silently does nothing.
• value - the integer to write.

Outputs

• client - the same handle, now carrying the patch. Wire it into the next Set node or into Run.

Install

Standard Yogurt Nodes install. ComfyUI Manager → search "ComfyUI-YogurtNodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/yogurt7771/ComfyUI-YogurtNodes.git
cd ComfyUI-YogurtNodes && pip install -r requirements.txt

Then restart ComfyUI.

Where people get burned

The whole failure class here is "the patch didn't take and nothing told me." A wrong node, a wrong key, or a type mismatch - writing an int where the remote expects a float usually converts fine, but writing an int into a field the remote defines as a combo or string won't. The way to debug is to look at the workflow JSON: open the remote workflow's API format, find the node, and copy the input name exactly. If the field you're patching is actually a widget value inside the node's inputs, the key is the widget's name. When you're sure it should work and the remote output is unchanged, that's where to look. And remember the client chain is ordered: if you patch after Run instead of before, the patch never ships - Run is a terminal step, everything Set must come first.