RunningHub Workflow ID
Point a run at the right cloud workflow
- STRING
Let's be honest up front: this is a text box with a job title. It holds one string - the id of a workflow hosted on RunningHub - and hands it downstream as a typed value. That's the whole node.
But the reason it exists is real. RunningHub is a cloud ComfyUI service, and the Addoor RHAPI nodes let your local graph drive a workflow that lives on their servers. To run one, you have to tell the API which workflow, and RunningHub identifies workflows by an id. RunningHubWorkflowID is the node that carries that id.
How it works
There's exactly one input, workflow_id, a single-line string, and one output, STRING. You paste your workflow's id in, and it emits it. That's it. No validation, no lookup - it's a labeled slot in the graph.
Why not just use a primitive text node? Two reasons, both about not shooting yourself in the foot. First, it's self-documenting: a node literally called "RunningHub Workflow ID" is obvious six months later when you reopen the graph, in a way a bare string node next to five other bare string nodes is not. Second, it keeps the id in one place. When you clone a graph to point at a different cloud workflow, you change one node instead of hunting through the canvas.
Using it
Grab the id from RunningHub - it's in the workflow's URL or its detail page. Drop it in, wire the STRING output into whichever RHAPI node kicks off the remote run. You'll typically have this sitting next to RunningHubInit (which handles your API key) and a chain of RunningHubNodeInfo nodes (which set the inputs). Together they say: this key, this workflow, these overrides - go.
Anything to watch for
Not much, because there's not much node here. The one failure mode is a wrong or stale id: RunningHub will reject a run pointed at a workflow that doesn't exist or isn't yours, and the node itself won't warn you because it never checks. Copy-paste the id rather than retyping it, and if a run bounces with a "workflow not found"-style error, this is the first place to look.
Installing ComfyUI-Addoor
Through ComfyUI Manager: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. Or by hand:
cd ComfyUI/custom_nodes
git clone https://github.com/Eagle-CN/ComfyUI-Addoor.git
cd ComfyUI-Addoor
pip install -r requirements.txt
Restart, and the RHAPI nodes appear under 🌻 Addoor. None of them generate images on your machine - they're glue for scripting RunningHub's cloud from a graph. If that's not what you're doing, you can skip this whole submenu.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| workflow_id | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |