Subgraph Labels

Subgraph Labels is the node you reach for once you've discovered that ComfyUI lets you collapse a whole section of a workflow into a subgraph - and then realized that a box full of anonymous input/output ports is only marginally better than the spaghetti it replaced. It assigns display labels to the subgraph's ports, up to 10 of them, so when you look at the collapsed node you can actually tell which wire is the prompt and which is the seed.

Here's the thing you need to know before anything else: this node is experimental, and the pack itself says it "requires subgraph support in your ComfyUI version." Subgraphs are a recent ComfyUI capability, part of the v3-era frontend work. If your ComfyUI doesn't have them, this node will load but there's nothing for it to label - it'll just sit there looking like a row of empty text fields. That's not a bug; that's the prerequisite being missing.

How it works

The node has ten string inputs, label1 through label10, all of them socketless - you type into the widgets, nothing gets wired in, and nothing comes out. Its outputs list is empty, and its execute function is a no-op. It is, in other words, pure UI decoration, in the same family as Simple Title but aimed at subgraph ports instead of the open canvas.

The interesting part is the frontend behavior: when the node is inside a subgraph, each widget renders as a compact text label rather than a normal input field. Type prompt into label1, and the corresponding port of the subgraph is labeled "prompt" where the wire attaches. Outside a subgraph it degrades gracefully to a plain string widget - which is exactly what you'll see if your ComfyUI version doesn't have subgraph support yet.

When it's worth using

Honestly? Only if you're already deep into subgraphs. If you're a beginner, subgraphs are a "later" feature - the KB's ecosystem notes that ComfyUI is a steep learning curve, and subgraph organization is firmly in the advanced half of it. But the moment you have a workflow where the same subgraph gets reused, or where a collapsed box's ports are indistinguishable at a glance, ten text labels are the difference between "which input is the mask again" and actually knowing. It's also genuinely useful for screenshots and shared workflows: a labeled subgraph reads like a component with a documented interface, which is more than most ComfyUI graphs can claim.

Installing it

Part of Nifty Nodes for ComfyUI (Stibo/comfyui-nifty-nodes). ComfyUI Manager → search "Nifty Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/Stibo/comfyui-nifty-nodes

Restart. The pack targets the v3 API (comfy_api.latest), so update ComfyUI if the pack doesn't load - and keep it updated, because subgraph support specifically lives on the newer frontend. No model downloads, no extra dependencies.

The honest bottom line

This is the most situational node in this pack's utils drawer. If you don't use subgraphs, you don't need it and nothing about your workflow will suffer. If you do use subgraphs, it's a small quality-of-life win that costs you nothing to drop in - and it's the kind of node you install once, use constantly, and never think about again.