工作流说明 (Workflow Description)

Sharing a ComfyUI workflow means sharing a JSON file - often embedded right in a PNG's metadata, which is exactly how "workflow included" became a community norm in the first place. But a raw graph of nodes and wires doesn't tell the person who opens it how to use it, what to change first, or that you fixed something since they last downloaded it. WorkflowDescription is a note node for exactly that: drop it into your graph, write your instructions in Markdown, and it renders as a formatted panel instead of a wall of plain text - with an optional "this version has changes" prompt the first time someone opens a newer copy.

It's part of ComfyUI-Danbooru-Gallery, a 23-node pack from a solo author - self-described as their first custom node, "built with the assistance of AI" - originally paired with a companion project called ShiQi_Workflow. Given the pack's whole reason for existing is one fairly elaborate template workflow, it tracks that its author built a documentation node into the same package: if you're handing people a complicated multi-node graph, you want a way to explain it that travels with the file.

How it works

Unlike almost every other node in this pack, WorkflowDescription has no inputs and no outputs - the schema is empty on both sides. That's because it isn't part of the execution graph at all; it's a UI element that happens to live on the canvas. You place it, you type Markdown into it (the node's own description calls out Markdown rendering by name), and it just sits there - nothing wires into it, and it wires into nothing. ComfyUI still flags it internally as an "output node" so the graph doesn't try to prune it as dead code with no downstream consumer, but functionally it's closer to a sticky note than a processing step.

The other half of what the description promises is version awareness: a "first open of this version" prompt. The practical read is that you bump a version marker when you update your workflow, and anyone who already has an older copy gets shown your note again the next time they open the new one - handy if you're iterating on a shared template and don't want people to miss that something changed. None of that shows up as a typed input in the schema, which tracks: it's a front-end widget, part of the JS extension side of this pack, configured directly on the node rather than wired from elsewhere.

What to actually put in it

There's nothing to configure in the socket sense - this is a type-and-go node. Treat it like a README stapled to the workflow itself: what the graph does, which nodes need a model or API key filled in before it'll run, and what changed since the last version if you're iterating in public.

Installing it

Via ComfyUI Manager: search "ComfyUI-Danbooru-Gallery," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Aaalice233/ComfyUI-Danbooru-Gallery.git
cd ComfyUI-Danbooru-Gallery
pip install -r requirements.txt

then restart. This node is pure front end/Markdown rendering, so it doesn't personally need the pack's heavier dependencies (aiohttp, aiosqlite, psutil) - but everything installs from the one shared requirements.txt, so there's no way to grab just this node.

Common issues & troubleshooting

The node shows up blank, or the Markdown doesn't render. This pack ships its rendering as a JS front-end extension, registered via WEB_DIRECTORY at load time - the README's own troubleshooting section says to check that registration succeeded in the console log on startup, and to clear your browser cache and refresh if the panel isn't loading. That's the fix for any of this pack's front-end panels, not specific to this node.

Labels or menus are in Chinese. Multi-language support is one of the pack's built-in JS extensions, but Chinese is the default. Other users report a gear/settings icon elsewhere in the pack that switches it to English.

Nothing to wire it to - is that broken? No. Empty inputs and outputs are correct for this node. If a downloaded workflow shows a disconnected WorkflowDescription node floating in the corner, that's by design, not a missing connection.