RH Settings

This is the node you set up first and then never think about again. RH_SettingsNode doesn't generate anything - it's the little box that holds your RunningHub credentials and which workflow you're pointing at, and hands all of that to the rest of the pack as one bundle. If you got an auth error somewhere in a RunningHub graph, this is almost certainly the node you need to look at.

To place it: ComfyUI_RH_APICall is the plugin that lets your local ComfyUI reach out and run a workflow that lives on RunningHub, a cloud ComfyUI host, on their GPUs - then pull the results back into your graph as normal images, video, latents, audio, or text. RunningHub is a real and busy platform (people compare it head to head with RunPod and MimicPC), so if you're here you're wiring your machine up to run something on theirs. Every node in the pack that touches the network needs to know your key and your base URL. Rather than pasting that onto each one, you set it once here.

What it actually outputs

The single output is a STRUCT - the pack labels it apiConfig. That's the whole point of the node: it packages your three settings into one object you wire into everything else. The image uploader, the audio and video uploaders, and the main execute node all have an apiConfig input, and they all get fed from this one Settings node. One source of truth for your credentials, one wire fanning out.

The three fields that matter

There are only three inputs and you'll touch all of them:

• apiKey - the key you get from your RunningHub account. This is the field. Register on the site, copy your key from the dashboard, paste it here. Blank by default, and a blank key is the number-one reason a graph errors the moment it hits the network.
• workflowId_webappId - which cloud thing you're running. For a saved RunningHub workflow, this is that workflow's ID. If you're calling one of their AI WebApps instead, it's the webapp ID (and you'll flip is_webapp_task on over at the execute node). Get the ID from the workflow's page on RunningHub, not from anything on your local canvas.
• base_url - defaults to https://www.runninghub.cn. Leave it unless you know you should change it (see below).

Installing it

No models, no heavy Python deps - the generation happens on RunningHub's hardware, not yours, so install is quick:

• ComfyUI Manager: open Manager, search ComfyUI_RH_APICall, install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/HM-RunningHub/ComfyUI_RH_APICall, then restart ComfyUI.

Then make a RunningHub account, grab your API key, and drop it in here. The pack ships example workflows in its examples/ folder - open one of those and you'll see this Settings node already wired into the rest.

Where people get burned

The classic one is the .cn vs .ai mismatch. The default base_url points at the China domain (runninghub.cn), but a lot of people register on the global runninghub.ai. Your key is tied to the site you signed up on, so if you made a .ai account and left base_url on the default, auth fails and every downstream node throws. Match base_url to where your account actually lives.

After that it's the boring stuff: a blank or mistyped apiKey, or a workflowId_webappId copied from the wrong place. And keep in mind what this node implies - your key plus whatever you send gets handed to a third party's servers, which is a different privacy posture than staying fully local. Nothing shady about it; just the honest cost of borrowing someone else's GPUs. Treat the key like the credential it is and don't paste it into a graph you're about to share publicly.