Workflow Organization: Groups, Notes, and Reroutes

When a Workflow Outgrows a Single Screen

The default text-to-image workflow has seven nodes and is easy to read at a glance. A production workflow for character-consistent portrait generation with ControlNet, LoRA, IPAdapter, ADetailer, and tile upscaling might have 40–60 nodes. Without organization, the canvas becomes an impenetrable tangle of wires crossing each other, and finding the node you want to adjust takes longer than running a generation.

ComfyUI provides three tools for organization that do not affect how the workflow runs — they only affect how it looks: group nodes, note nodes, and reroute nodes. Investing five minutes in organization at the end of building a complex workflow saves significant time every subsequent use.

Group Nodes: Visual Sectioning

A group node is a colored rectangle that you draw around a set of related nodes to label them as a section. The group has a label at the top. When you move the group, all the nodes inside it move together.

To add a group node:

• Right-click on empty canvas space and select Add Group.
• A light-colored rectangle appears. Drag its edges to resize it around the nodes you want to group.
• Double-click the label at the top of the group to rename it (e.g., "Text Encoding", "Sampling", "Upscaling Pipeline").
• Right-click the group header to change its color. Pick a color that corresponds to the section's purpose — you can establish your own conventions, such as blue for loading, green for sampling, orange for post-processing.

Groups do not create any logical boundary — nodes inside a group are no different from nodes outside one. The group is purely visual. You can move nodes in and out of groups freely by dragging them.

A practical color convention to start with:

• Blue/purple: Model and LoRA loading sections
• Green: Core sampling / KSampler area
• Orange: Post-processing, upscaling
• Red: Output / save nodes

Note Nodes: Documentation in the Canvas

Note nodes display plain text directly on the canvas. They are not connected to anything — they are just labels or explanations you leave for yourself (or for people you share the workflow with).

To add a note node: right-click → Add Node → utils → Note. A yellow text box appears. Click inside it to type.

Common uses for notes:

• Explain what a custom node does or why a setting has an unusual value.
• List the models required for the workflow at the top of the canvas, so anyone loading it knows what to download.
• Label sections with text when color alone is not enough.
• Add a version number or date to track when you last updated the workflow.

Keep notes short. A note that says "ControlNet depth preprocessing section" is useful. A note with three paragraphs explaining the theory of ControlNet will be ignored by anyone (including future you) after the first read.

Reroute Nodes: Untangling Wire Spaghetti

When a workflow grows, wires start crossing each other. A MODEL wire from a Load Checkpoint node on the left might need to cross over an IMAGE wire going in the opposite direction to reach a LoRA stack on the right. These crossings make it hard to trace which wire connects which nodes.

A reroute node is a tiny node with one input and one output of the same type. It acts as a bend point in a wire — you can route the wire around obstacles by placing reroutes at corners.

To add a reroute: right-click on a wire to open the wire context menu and select Add Reroute. A small dot appears on the wire where you clicked. Drag this dot to reposition the bend point. Add multiple reroutes to create a path that goes around other nodes.

Reroutes can also be added from the node menu: right-click on empty canvas → Add Node → utils → Reroute. Connect it manually by dragging a wire to its input and another wire from its output.

Bypassing Nodes

Bypassing a node temporarily disables it — the node is skipped and the workflow runs as if it does not exist, with the input passing directly to the downstream node. The bypassed node turns purple/violet to indicate it is inactive.

To bypass a node: select it and press Ctrl+B (Cmd+B on Mac). Press Ctrl+B again to re-enable it.

Bypass is useful for A/B testing. For example: you have ADetailer in your workflow. You want to compare the output with and without face restoration. Bypass the ADetailer node, run the generation, then re-enable it and run again. Same seed, same settings, the only difference is the bypassed node.

Bypass is also useful during workflow development — if a new node you added is causing issues, bypass it to confirm the rest of the workflow runs correctly, then investigate the problematic node in isolation.

These three tools — groups, notes, reroutes — do not change what a workflow does. They change how easy it is to work with. Build the habit of adding groups and labels when you finish a complex workflow, and you will thank yourself the next time you open it.