Audio Save to Path

ComfyUI's built-in Save Audio node drops files into the output folder with an auto-generated name and counter. Fine, until you want a specific file at a specific path - a fixed name, a particular folder, something a downstream script expects to find. That's the gap this node fills: you give it audio and an exact path, and it writes the file there, name and all.

It shows up in audio workflows - TTS output, generated music, audio pulled out of a video - anywhere the last step is "put this exact file here." Being able to name the file and choose its folder is the whole reason to prefer this over the default saver, especially in automated pipelines where the next tool in line is looking for a known filename.

How it works

It takes the audio and writes it to the path you specify. The file extension in that path determines the format - end it in .mp3 and you get an MP3, .wav for WAV, and so on (within what the underlying library supports). It's an output node, so it triggers execution on its own without needing to feed a preview.

Inputs and outputs

• audio - the AUDIO to save.
• path - the full destination path and filename (default ./audio.mp3). The extension sets the format.
• overwrite - a boolean, default true. Left on, it clobbers any existing file at that path; set it false to protect a file already there.

There are no outputs - this is a terminal save node. It does its work and the branch ends.

Installing it

Heads up: the pack's README groups its nodes by file and its published list is a bit behind the actual code - this audio node isn't in that index yet (the author notes the repo is still early and lacks per-file docs). So the safe install is the whole repo rather than trying to grab one file. Easiest is ComfyUI Manager: search Various ComfyUI Nodes by Type (comfyui-various), install, restart. Or clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/jamesWalker55/comfyui-various

Restart ComfyUI. No models, and no special audio dependencies beyond what ComfyUI already carries for audio nodes.

Common issues

The big one on a hosted or serverless runner like this platform: the filesystem is ephemeral and you don't own it the way you do locally. A path like ./audio.mp3 writes relative to the executor's working directory, which is temporary - the file won't be sitting on your own disk afterward, and it may not survive past the run. This node is built for a local ComfyUI where you control the folders and want a file to land in a known spot. In the cloud, to actually get audio out, you're generally better off with the standard Save Audio path that routes into the platform's outputs.

Locally, the usual snags are ordinary file-system ones: the target folder has to exist (writing to a directory that isn't there will fail), and you need write permission to it. And mind the overwrite flag - with it on (the default), re-running the graph silently replaces the previous file, which is fine for iterating but will happily overwrite something you meant to keep. Flip it off when the file matters.

If the node loads red as missing when you open a workflow, the pack simply isn't installed - Manager's "Install Missing Custom Nodes" or a clone of the repo above resolves it.