RH Settings

Every good cloud romance starts with an API key, and RH Settings is where you paste yours. It's the configuration hub of the ComfyUI-RunningHub pack: you tell it who you are (API key), where the server lives (base URL), and which cloud workflow you want to run (workflow ID), and it hands the whole bundle downstream as a single api_config structure. The Execute nodes - RH Execute Workflow and RH Execute AI App - are the only ones that take that structure, so this node is the front end for the pack's main job: running a workflow that lives on RunningHub's GPUs instead of yours.

If you're new to the RunningHub half of this story: RunningHub is a cloud ComfyUI platform (Chinese site runninghub.cn, international runninghub.ai) where you build or clone workflows and run them on their machines, paying per task or per minute. The pitch, echoed all over r/comfyui, is that it turns "download six nodes, fight three dependency conflicts, hunt 40GB of models" into "paste a URL, pay two cents, get a result." This node is the local half of that bridge.

What you actually set

Three fields, and two of them matter:

• api_key - your RunningHub key, a 32-character string from the account menu. The tooltip says it plainly: 32 characters. If you paste something shorter, it's wrong.
• base_url - defaults to https://www.runninghub.cn. If you're outside China, this is the classic first-burn: switch it to https://www.runninghub.ai or every request goes to the wrong region's API and you get auth or not-found errors. The tooltip gives you both URLs so you can't miss it.
• workflow_id - the ID from a RunningHub workflow's URL. This is the workflow you built (or cloned) on the website.

The output is one socket, api_config, of the pack's custom STRUCT type. You don't read anything from it - you just wire it into an Execute node and forget it exists.

The gotcha most people hit first

RH Settings is not required for every node in the pack. The Task nodes (status, cancel, outputs) and the Model nodes (text-to-image, image-to-image, video, audio) each carry their own api_key/base_url/workflow_id fields directly on the node. Only the two Execute nodes take the api_config STRUCT. So don't go wiring RH Settings into everything expecting it to be accepted - it connects where the schema says STRUCT, and nowhere else.

The other one: the node logs a warning if the key is empty but still produces a config, so an empty key won't loudly crash. It fails downstream, at the Execute node, usually as a cryptic "authentication failed." Fill the key first.

Install

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

Or search "RunningHub" in ComfyUI Manager. Restart, find RH Settings under the RunningHub category. Requirements are light - requests, websocket-client, Pillow, numpy - no giant model downloads.

One security note worth keeping, because the KB's API-node essay hammers it: a node that carries your API key and phones home by design is exactly the shape of thing that has been weaponized in this ecosystem. This is a widely-distributed open pack, but it's still arbitrary Python holding a credential. Paste the key in, keep the key out of shared workflows, and know your data - prompts, images - leaves the machine for RunningHub's servers the moment you queue.