Salt Workflow Output

Most of this pack is generic - masking filters, string utilities, image processing you'd reach for in any ComfyUI graph regardless of where it runs. SaltOutput is the exception. It exists specifically for Salt AI's own hosted platform (getsalt.ai), the company behind this node pack, which lets you deploy a ComfyUI workflow and call it like an API or run it through a Discord bot. This node is how a workflow declares "here's my labeled result, and here's what type it is" so the platform - or whatever's calling your workflow - knows what to expect back.

What it does

It's an output/terminal node (is_output_node is true, so it doesn't feed anything further downstream). You give it output_name and output_desc - a label and description that become part of your workflow's output schema when deployed through Salt's platform - an output_type picked from a genuinely wide list (PNG, JPEG, GIF, WEBP, AVI, MP4, WEBM, MP3, WAV, STRING), and output_data, typed as a wildcard * so it'll accept whatever you actually wire into it. Three optional fields matter only for animated/video formats: video_audio (an AUDIO input, for muxing a soundtrack into a video output), animation_fps (1–60, default 8), and animation_quality (DEFAULT or HIGH).

When you'd actually reach for this

If you're just running a workflow locally, or on comfy.icu directly, the standard SaveImage/SaveVideo nodes cover almost everything you need - this node's real value is the structured, typed, multi-format output contract it gives you when a workflow is meant to be deployed and called externally through Salt's own platform, where output_name/output_desc become part of the API response shape rather than just a file dropped on disk. Unless you're specifically building for Salt AI's hosting layer, you probably don't need this node.

Installing it

ComfyUI Manager: search SaltAI-Open-Resources. Manual install:

cd ComfyUI/custom_nodes
git clone https://github.com/get-salt-AI/SaltAI

Restart ComfyUI. No extra dependencies for this node specifically.

Common issues

Make sure output_type actually matches what you're feeding into output_data - picking MP4 and wiring in a single still image, or picking PNG and wiring in a video batch, is a mismatch the node can't silently fix for you and will produce a broken or empty export. animation_fps and animation_quality only apply when your output_type is one of the animated/video formats - they're simply irrelevant for a still PNG/JPEG/STRING output, so don't expect changing them to affect a still-image export. And since this node's whole purpose is tied to Salt's own hosted deployment model, if you're not actually deploying through their platform, don't be surprised if it feels like it's doing nothing useful in a purely local graph - that's expected, it's built for a context you may not be in.