RH Video Uploader Path

Running a video-to-video or a frame-interpolation job on RunningHub means the cloud workflow needs your video - and your video is on your disk, which their servers can't see. RH_VideoUploaderPath closes that gap: you give it the path to a video file, it uploads that file to RunningHub, and it returns the remote filename you then reference inside the cloud workflow.

This is part of ComfyUI_RH_APICall, the plugin that runs workflows on the RunningHub cloud instead of your own GPU. The reason an uploader is necessary at all is simple and someone ran into it on r/StableDiffusion the hard way: nodes that read local files "can't connect to your PC" once the workflow is executing in the cloud. So any input the remote graph needs - a video, in this case - has to be pushed up first. This node is that push for video.

How it works, and why it takes a path

Notice the input is a path string, not a video wire. Images in this pack ride the normal ComfyUI IMAGE type, but video and audio come in as a filesystem path - you tell the node where the file is and it reads and uploads it. You point it at, say, C:\clips\input.mp4, and it sends that file to RunningHub through the API, returning the name the file now has on their side. That returned filename is what you feed into an override so a specific node in the cloud workflow uses your uploaded clip.

The inputs and output that matter

• video_path (STRING) - the path to the local video file to upload. A plain string; type or paste the full path.
• apiConfig (STRUCT) - the credential bundle from RH_SettingsNode. Wire your Settings node in here so the uploader knows which account and endpoint to push to. No config, no upload.

The output is filename (STRING) - the remote name of your uploaded video. Route it through a NodeInfoList override into the main execute node, which is where the cloud workflow actually runs and consumes it.

Installing it

The pack installs in one go, with no models or heavy dependencies because the work happens on RunningHub's hardware:

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

Set your API key and workflow ID on the RH_SettingsNode (not here - this node just consumes that config), and lean on the pack's examples/ folder to see how the upload wires into a full run.

Where people get stuck

The most common failure is a bad path: a typo, a relative path when it needed to be absolute, or backslash quoting weirdness on Windows. If the node can't find the file, it can't upload it - double-check the path resolves to a real file first. Next most common is credentials, which surface at the first networked node: a blank apiKey on the Settings node, or the .cn/.ai domain mismatch where your account lives on one domain and base_url points at the other.

And if the upload succeeds but your clip doesn't seem to take effect, that's the override, not the uploader - the NodeInfoList entry is targeting the wrong node ID or field in the cloud workflow, so it ran on its default input. The pack also ships a plain RH_VideoUploader; both take a string here, so use whichever matches the example workflow you started from. As always, your video leaves your machine for a third party's servers - upload only what you're comfortable handing over.