Print (CCN)

Sometimes you don't need a fancy debug panel - you need to know whether a branch even ran. That's this node's whole job. It takes whatever text you typed, prints it to the ComfyUI console as [CCN] <text>, and passes the trigger through so you can drop it inline without breaking your wire.

The pack author's framing for the whole collection is "nodes I needed" - and honestly, a print node is the kind of thing you stop noticing until you're staring at a workflow that produced nothing and wondering which branch is dead.

How to use it

Drop it into a wire that would otherwise run straight through. The text field is multiline and defaults to "Hello", so you'll want to change that. The trigger input is ANY typed, which per ComfyUI's type system means it accepts a model, a latent, a string, whatever - the node just forwards it untouched. So the shape is: upstream → trigger → Print → trigger → downstream.

Two outputs back on the wire: whatever you passed in, unchanged. The real output is a line in your terminal.

The timing gotcha is worth knowing before it bites you. Print is not an output node, so it only executes when something downstream actually requests its trigger output. Wire the trigger into a Preview Image, a Save node, a sampler - anything that runs - and it fires. Park it with nothing consuming its output and ComfyUI's cache can skip it entirely, which makes it look broken when it's just idle.

Install

It's one of the ~20 nodes in ComfyCollectorNodes, so install the pack once:

cd ComfyUI/custom_nodes
git clone https://github.com/valkymaera/ComfyCollectorNodes

then restart ComfyUI. ComfyUI Manager works too - search "ComfyCollectorNodes". No models, no extra dependencies; the pack has zero Python requirements beyond what ComfyUI already ships.

Where people get burned

The console, not the UI. The text goes to the terminal where you launched ComfyUI (or the Manager log viewer) - it does not show up as a node widget or a floating toast. If you're looking at the canvas wondering where the output went, that's your answer. The other footgun is the caching one above: if the node never fires, it's usually because nothing downstream is pulling its output, not because print is broken. Wire the trigger into something that runs, and you'll see the line.