Koolook Publish Result

Koolook Publish Result is the closing bracket of the Publish family. Where Publish Input declares what a published workflow gets fed and Publish Output declares where it writes, this node reports what actually happened - a resolved path, folder, or status string that the external app shows after the run finishes.

It's the simplest node in the group, and it's deliberately that way. You wire in the resolved result - typically the WRITE_file_path from a path builder or a status string from a saver - and it passes it back out as its single result output while flagging itself as an output node, so the published-setup runner knows this is where the run's outcome lives. One input, one output, no settings.

How it works

The input is a multi-line string, result, with one tooltip sentence as the whole spec: "Resolved result path, folder, or status string to show after the external app run finishes." The output is the same string, passed through unchanged. That's the mechanism. The value is in what you feed it: a real, resolved path (not a template, not a placeholder), because whatever the runner displays is only as honest as the string you put in.

Marked is_output_node, which in ComfyUI terms means the workflow treats it as a terminal - it's meant to sit at the end of the published graph, the way a Save node or Show Text sits at the end of a normal one. If you're debugging a published setup and the external app reports nothing, the first thing to check is whether a Publish Result is actually in the graph and wired.

Where it fits

The full published chain reads: Publish Input (source contract) → Router (fan-out) → Publish Output (writer contract) → the actual writers → Publish Result (outcome). The Result node is the one the app reads last. It also works fine as a standalone "echo my path back to me" node inside a normal workflow if you want a clean terminal for a path - the Publish machinery doesn't need to be active for the passthrough to work.

Install

Part of the ComfyUI-Koolook pack. ComfyUI Manager → Install Custom Nodes → Git URL:

https://github.com/malkuthro/ComfyUI-Koolook.git

Or:

cd ComfyUI/custom_nodes
git clone https://github.com/malkuthro/ComfyUI-Koolook.git

Restart and it's under Koolook/Publish. No models, no dependencies - a string passthrough. And the pack's standing rule: install once. A Manager install at custom_nodes/koolook/ plus a git clone copy creates a parallel install that double-registers and corrupts the workflow store on every boot until you remove one folder.

Common issues

• The app shows nothing after a run - no Publish Result in the graph, or its input isn't wired. This node is how the runner gets its "done" signal; without it, the external surface has nothing to report.
• It reports a template instead of a path - you fed it an unresolved string like %04d or a plain variable name. Give it the resolved result from the writer/path builder.
• Result is wrong or stale - trace what's feeding it. It faithfully echoes whatever it's given, so a wrong report means a wrong input, not a bug here.