RunningHub Image Uploader

Here's the problem this solves. RunningHub runs your ComfyUI workflow on their servers. If that workflow needs an input image - a reference for img2img, a control image, a face - the cloud has no idea what's sitting on your laptop. You have to push the image up first and then tell the remote workflow its filename. This node does the push.

It's a genuinely necessary piece of the RHAPI puzzle; without it, any cloud workflow that starts from your own images is a non-starter.

How it works

Two inputs: api_key (your RunningHub credential) and image (a standard ComfyUI IMAGE, so it can come from a Load Image node or anything upstream). The node uploads that image to RunningHub and returns filename - the name the file now has on their side.

That filename is the whole point. You take it and feed it into a RunningHubNodeInfo override so the remote workflow's Load Image node points at the file you just uploaded. Upload here, reference there. This is the standard dance for driving a cloud image-to-image job from a local graph - community folks doing the same thing on RunningHub reach for equivalent "upload to RH" nodes for exactly this reason.

Using it

Wire an image into image, your key into api_key, run it, grab the filename output. Then in your RunningHubNodeInfo chain, set the remote LoadImage node's field to that filename. If the remote workflow takes several images, you use several of these uploaders, one per image, each producing its own filename.

Worth knowing

The obvious one: your image leaves your machine and lands on a third party's servers. That's the deal with any cloud-generation service, but it's worth saying plainly if you're feeding it anything private.

The api_key plaintext caveat applies here too - don't ship the key inside a shared workflow. And if an upload fails, it's almost always auth (bad key) or a network hiccup to RunningHub, not the image itself.

One sequencing thing to keep straight: the upload happens when this node executes, and the filename it returns only becomes valid after that. So the uploader has to run before the node that launches the remote workflow - you can't reference a filename that hasn't been uploaded yet. In a normal graph that ordering falls out naturally from the wiring, but if you're bypassing nodes or building the run conditionally, make sure the upload isn't getting skipped ahead of the reference to it.

Installing ComfyUI-Addoor

ComfyUI Manager is simplest: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. 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 ComfyUI; find it under 🌻 Addoor / RHAPI. Like the rest of that submenu, it only does anything if you've got a RunningHub account - it's an uploader for their service specifically, not a general image host.