RH Video Uploader

Video jobs are exactly the kind of thing you want to offload - they're slow, VRAM-hungry, and often chain several models together. ComfyUI_RH_APICall lets you run them on RunningHub's GPUs instead of your own, and RH_VideoUploader is the node that gets your source clip up there. Hand it a local video, it uploads to RunningHub, and it returns the remote filename the cloud workflow will point at.

The whole pack bridges your local ComfyUI to RunningHub's cloud: you fire a saved workflow on their servers and pull the results back. The catch that makes an uploader necessary is that the workflow runs there, not on your PC - a point one r/StableDiffusion user hit when their local file-loading node "can't connect to my PC" from the cloud side. Anything the remote graph needs from your machine has to be uploaded first. For video, this is that step.

How it works, and why it takes a path

The input is a path string, not a video wire. Images in this pack move on the standard ComfyUI IMAGE type, but video and audio are handled as filesystem paths - you tell the node where the file is and it reads and uploads it. Give it something like C:\clips\source.mp4 and it sends that file to RunningHub via the API, returning the name the file has on their side. You feed that filename into an override so a specific node in the cloud workflow uses your clip.

The inputs and output that matter

• video (STRING) - the path to the local video file to upload. A plain string; the full path to the file.
• apiConfig (STRUCT) - the credential bundle from RH_SettingsNode, telling the uploader which account and endpoint to push to. Wire your Settings node in; without it, no upload happens.

The output is filename (STRING) - the remote name of your uploaded video, which you route through a NodeInfoList override into the main execute node that runs the workflow.

Installing it

The pack installs in one step, with no models or heavy dependencies since the GPU work is remote:

• ComfyUI 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.

Put your API key and workflow ID on the RH_SettingsNode (this node only consumes that config), and start from a graph in the pack's examples/ folder to see the upload wired into a real run.

RH_VideoUploader vs RH_VideoUploaderPath

The pack ships two video uploaders, and in the current node definitions both take a string path and both return a filename. If you're staring at both wondering which to use, the short answer is: use whichever one the example workflow you started from uses - functionally you're giving each a path and getting a remote filename back. Don't overthink the pair.

Where people get stuck

The two reliable failure modes are a bad path - a typo, a relative path that should have been absolute, or Windows backslash quoting - and credentials, which surface at the first networked node: a blank apiKey, or the .cn/.ai domain mismatch between your account and your base_url. Make sure the path resolves to a real file and the Settings node matches the domain you signed up on.

If the upload succeeds but the clip doesn't change the output, it's the override, not the uploader: your NodeInfoList entry is pointing at the wrong node ID or field in the cloud workflow, so it ran on a default input. And the pack-wide reminder - your video is sent to a third party's servers and processed there, a different privacy and cost model than staying local, so upload only what you're comfortable sharing.