PDNetworkOutput

First, the thing nobody tells you on a page like this: PDNetworkOutput no longer exists as a separate node. In Pipedream 0.2.0 the author renamed it to 💭 PD Output Absolute and kept PDNetworkOutput registered as a backward-compatibility alias, so old saved workflows don't break. Search for it in your node list and you'll find the emoji-prefixed 💭 PD Output Absolute instead. Both names route to the same code. Everything below is that node.

What it's for

If you've ever handed a render to a review department, you know the drill: it has to land on \\RENDER01\Output\DITC_Ep01\sq010\sh020\ with a correctly formatted filename, not in your local output folder. That's this node. It resolves a token template against a Pipedream context, builds a full absolute or UNC path, creates any missing directories, and writes the image batch there.

The inputs that matter

• images - the IMAGE tensor from your VAE decode. This is an output node; it replaces (or sits beside) ComfyUI's built-in Save Image.
• base_path - the root you're writing to: \\RENDER01\Output on Windows, /mnt/render01/output on Linux. UNC prefixes are preserved, and forward slashes get normalized to backslashes for you on Windows.
• template - the filename pattern, defaulting to {project}/{sequence}/{shot}/{shot}_{version}_{date}. Subfolders are fine inside the template; the node creates them.
• frame_padding (default 4) and extension (png, exr, jpg, webp) - how the {frame} placeholder pads out, and what format gets written.
• context - the PROJECT_CONTEXT from 💭 PD Project Context / Custom Context. Skip it and the built-in tokens like {date} and {time} still resolve, but your project metadata won't.

Output is a single written_path string (the final path of the first file written), handy if you want to log or display it.

The two toggles that bite

• create_dirs (default on) - creates the whole tree as it goes. Turn it off if you want a hard failure when a path is missing rather than silent directory creation.
• overwrite (default off) - this is the one that gets people. Re-run the same workflow and the file already exists, so the node skips writing and prints an error to the console. That's a feature for shot work (nobody wants a silently clobbered approved frame) and a trap for iteration workflows until you understand it. A batch of images also gets _0001, _0002… suffixes appended automatically, so one batch becomes a proper sequence.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/TheOnlyAaron/comfyui-pipedream

Restart ComfyUI, or install "Pipedream" via ComfyUI Manager. No extra dependencies, no model downloads - this pack is pure plumbing, which is the whole pitch.

Gotchas

• The node talks to whatever filesystem it's pointed at; if the share is unmounted or the permissions are wrong, you get a Python traceback in the console. Check the path exists and is writable before you blame the node.
• If you load an old workflow that references PDNetworkOutput, it still runs - that's the whole point of the alias. But new nodes you add will show up as 💭 PD Output Absolute, and the two are interchangeable in a graph.