RunningHUB API

RunningHub is a cloud ComfyUI platform - people host whole workflows there as "webapps," and you pay by the run instead of by the GPU. This node is the bridge: it submits a task to one of those webapps from your local ComfyUI, feeds it images if it needs them, waits for the job to finish, and pulls the result back. It's for the situations your own hardware can't handle, or where the workflow you want to use is published on RunningHub and nowhere else.

The catch, and it's a real one, is that this is a paid API with its own key and its own app IDs. You can't install it and fire it up like a local sampler. You need three things from RunningHub: an API key, the webapp_id of the app you're calling, and internet access to www.runninghub.cn. The pack itself is free and open source; the cost lives in the service you're calling.

How it works

Under the hood the node does a three-step dance against the RunningHub open API. It uploads whatever input images you've wired in (the node grows extra image slots as you connect them), submits a task to the webapp with your parameters, then polls the task status until it's done. The timeout field is your cap on that polling - it defaults to 600 seconds and can go up to 3600 (an hour), which is worth knowing because image-and-video webapps can run long. When the run completes it hands you the generated image and the URL where RunningHub stored the file.

The node_modifications field looks scary (a JSON blob with a default of []), but you almost never touch it. The frontend writes it automatically to describe which of the webapp's node parameters you've configured. Leave it alone unless you know what you're doing.

The inputs that matter

• api_key - from your RunningHub account. This is the whole gate; without it nothing else matters.
• webapp_id - the ID of the specific webapp you want to invoke.
• timeout - how long to wait for the run (60–3600s, default 600).

Outputs are image (the result as a normal IMAGE tensor, so it plugs straight into a preview or a Save Image node) and file_url (a STRING pointing at the file on RunningHub's storage).

Install

Same as any node in this pack - it ships in ComfyUI-WBLESS, which has no requirements.txt and no model downloads:

cd ComfyUI/custom_nodes
git clone https://github.com/LaoMaoBoss/ComfyUI-WBLESS

then restart ComfyUI. Or use ComfyUI Manager, search "ComfyUI-WBLESS," install, restart.

Troubleshooting

The two failure modes people actually hit: a wrong webapp_id (the API returns a task error, and you stare at a Chinese error message wondering what you typed wrong) and a too-short timeout for video jobs - bump it toward 3600. Because RunningHub is a China-centric platform, connection issues from elsewhere are usually network, not node, problems. And remember the task is billed in RunningHub's credits whether it succeeds or errors, so it's worth validating your key and webapp ID on a cheap job before pointing a big batch at it.

This is a niche node for a niche workflow: local-to-cloud orchestration. But if you've got a batch of prompts and a hosted app that does the heavy lifting, it turns your box into a Remote-Pilot for a service that costs you per run - which is a feature, as long as you don't leave a thousand-image queue unattended.