RunningHub Initialize

This is the "log in" node of the RunningHub set. RunningHub is a cloud ComfyUI service, and ComfyUI-Addoor ships a handful of nodes (the RHAPI submenu) that let your local graph drive workflows running on their servers. Every one of those needs to know who you are. RunningHubInit is where you hand over your API key.

How it works

One input: api_key, a single-line string. One output: STRING. You paste your RunningHub API key in, the node validates/initializes the session, and passes a value downstream that the rest of the chain uses. Wire that output into the other RHAPI nodes that need auth, and you've established the connection once instead of pasting your key into every node.

That's the sensible way to think about it - one place holds the credential, everything else references it.

In practice this is the first RHAPI node that runs. The rest of the chain - pointing at a workflow, setting inputs, uploading images, saving results - assumes the session is already established, so RunningHubInit sits at the top of the graph and its output flows down into whatever needs authenticated access. If you're wiring a full remote run and things fail immediately, check that this node is actually connected and executing before the others, not stranded off to the side.

Where to get the key

It's in your RunningHub account settings, under the API or developer section (their UI, not ComfyUI's). Copy it, drop it in, done. If you don't have a RunningHub account, none of this applies - the RHAPI nodes are pointless without one, because they're clients for that specific service.

The one thing to be careful about

Your API key is a credential, and this node holds it as plain text on the canvas. If you share the workflow - export the JSON, post a screenshot, hand the graph to a teammate - the key can ride along in the saved file. Strip it before you share, or wire the key in fresh on the other end. This is the same hygiene you'd use for any token; it just bites harder here because ComfyUI workflows get shared constantly, and a leaked key spends your RunningHub credits.

Beyond that, the usual: a wrong or expired key means every downstream RHAPI call fails, so if the whole chain errors out, check here first.

Installing ComfyUI-Addoor

Via ComfyUI Manager: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Eagle-CN/ComfyUI-Addoor.git
cd ComfyUI-Addoor
pip install -r requirements.txt

Restart ComfyUI. The node lands under 🌻 Addoor / RHAPI. Pair it with RunningHubWorkflowID (which workflow), RunningHubNodeInfo (what to override), and RunningHubFileSaver (bring the results back) to script a full remote run - none of which touches your local GPU.