RunningHub File Saver

The last node in the RunningHub round trip. You've initialized with your key, pointed at a workflow, set the inputs, and run it on RunningHub's cloud - now the results are sitting on their servers as URLs. RunningHubFileSaver downloads those files to your own disk and names them sensibly. It's the "bring it home" step.

How it works

The key input is file_urls, a FILEURL_LIST - the list of result links that comes back from the remote run. Everything else is about how to save them locally:

• directory - where they land (defaults to outputs).
• filename_prefix / filename_delimiter / filename_number_padding - the naming scheme. Defaults give you RH_Output_0001, RH_Output_0002, and so on. Padding controls how many zeros.
• file_extension - auto guesses from the file itself, or you can force png, jpg, txt, json, mp4, etc. Leave it on auto unless the guess comes out wrong.
• open_output_directory - a boolean that pops the folder open when it's done. Handy on a desktop, pointless on a headless server.

Out the other side you get output_paths (where the files went), previews (an IMAGE output so image results show right on the canvas), and file_types.

Why it's nicer than it sounds

A cloud run hands you raw URLs, which are a pain - they expire, they're not on your machine, and you'd otherwise be right-clicking and saving one at a time. This node grabs the whole batch, drops them in one folder with consistent numbered names, and previews the images so you can see what you got without leaving ComfyUI. For an automated loop dispatching dozens of jobs, that tidy naming is the difference between an organized output folder and chaos.

Watch for

The auto extension is a guesser - if a video or JSON result lands with the wrong suffix, set file_extension explicitly. And since these are downloads over the network, a flaky connection to RunningHub can leave you with partial files; re-run if a save looks truncated. The URLs are also time-limited on RunningHub's side, so save results while they're fresh rather than reusing an old file_urls list hours later.

Installing ComfyUI-Addoor

ComfyUI Manager: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. Manual route:

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

Restart, and it's under 🌻 Addoor / RHAPI. It's the tail end of the RunningHub client set - only useful once the other RHAPI nodes have actually run something in the cloud for it to fetch.