Dummy Out to trigger workflow

The node's own description is unusually blunt about what it's for: "Does nothing, used to trigger generic workflow output. A way to get previews in the UI without saving anything to disk." That's the whole node in one sentence - it exists purely because ComfyUI needs an output node somewhere in a branch for that branch to actually run and show you something, and this one gives you that trigger point without a Save Image (or equivalent) writing a file you didn't actually want kept.

Why "does nothing" is the point

A lot of debugging in ComfyUI comes down to wanting to see a mid-graph value - did this string come out right, is this image the one I think it is - without committing to saving it. Plugging a Save Image node in for every intermediate check clutters your output folder with throwaway files. KY_DummyOut sidesteps that: wire a value in, it echoes straight back out, and because it's marked as an output node, ComfyUI treats that branch as complete and renders whatever preview it can, with nothing written to disk.

Inputs and outputs

Five required inputs, any1 through any5, all wildcard-typed. Five outputs, mirrored one-to-one - any1 in comes back as any1 out, and so on for all five slots. Nothing is transformed; what goes in comes straight back out, unchanged.

Since it's marked is_output_node: true, this node is a valid terminal point in a graph on its own - you don't need to route its outputs anywhere further unless you actually want to keep working with the value.

Installing it

ComfyUI Manager: search ComfyUI-KYNode, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/yorkane/ComfyUI-KYNode

Restart ComfyUI. Nothing to it - no dependencies, no external calls, it's a pass-through.

Common issues

All five inputs are marked required in the schema, which is worth knowing before you drop this node expecting to use just one or two slots - if ComfyUI's validation treats an unconnected required socket as an error (the usual behavior for required inputs without a documented default), you may need to wire something into all five, even a throwaway constant, rather than leaving the unused ones blank. If you only care about previewing one value, this pack's own single-value siblings - KY_isNone or KY_First_NOT_EMPTY, both of which have a genuine single pass-through output - may be a cleaner fit than forcing all five sockets on this node.

Don't mistake this for a save node. If you actually need the result on disk - an image, a video, a file - this node explicitly does not write anything; reach for KY_SaveImageToPath, KY_SaveImageSequence, or KY_SaveVideo depending on what you're saving, and use this one only for the "just let me look at it" step.

Because it's wildcard-typed on every socket, ComfyUI won't stop you from wiring in wildly different types across the five slots - that's expected and fine, since the node makes no assumptions about what it's holding.