MiniMax H3 Image • Workflow Note

Let's get the scary part out of the way, because it's why you're probably here: H3WorkflowNote - "MiniMax H3 Image • Workflow Note" - is a text label. It displays text in your workflow and does nothing else. It has no outputs, no inputs beyond its own widgets, and it never touches generation. The text isn't even sent to MiniMax H3. It exists so bundled workflows can carry guidance inline - a "note" node, in the ComfyUI tradition of documentation nodes that ride along in shared workflow JSON.

The v15 compatibility story

So if you loaded a workflow and got "H3WorkflowNote is reported as missing," the fix is almost certainly just version drift. This node was added in v15, current workflows no longer depend on documentation-note nodes, but a saved workflow from a v15-era version still references the class. Update the pack, restart ComfyUI, and refresh the browser - and make sure it's a full stop of every ComfyUI process, because updating files without restarting does not replace node definitions already loaded into memory. Once you're current, the error goes away.

What it offers

What it actually offers, for the two seconds you'll spend on it: a section dropdown (quick start, models, settings, optional / experimental, troubleshooting) that labels the card visually, and a text field for your notes. The pack even ships a small frontend theme (web/js/h3_theme.js) that gives WorkflowNote nodes a distinct note-card color and a wider minimum width, so they read as documentation rather than as nodes. Since it renders in saved workflows, it's genuinely useful for annotating a shared graph - "select an image in every Load Image node before running" is the kind of note that saves the person you send a workflow to an hour of confusion.

Honest observations

A few honest observations. First, because it's compatibility scaffolding rather than a living feature, don't build your workflow around it - the README says current bundled workflows "no longer depend on documentation-note nodes," and the safest posture is to treat it as disposable. Second, it's a good test case for whether your install is current: if the node exists in your node list, you're on v15+; if a workflow complains it's missing, update. Third, and this is the design smell worth appreciating, the author kept it around precisely so old saved workflows don't break - deleting documentation nodes outright would have bricked every v15-era file floating around. That's a compatibility courtesy more pack authors should copy.

Install

Install is the same as the rest of the pack: ComfyUI Manager (search MiniMax H3 Image Studio) or git clone https://github.com/astropuzzo/ComfyUI-MiniMax-H3-Image-Studio.git into custom_nodes, then restart. No models, no dependencies beyond ComfyUI 0.30.0+ - this node needs nothing but ComfyUI itself. If you don't want it, delete it from your graph; nothing downstream will notice.