Nodes/comfyui_mindmap/MindMap Link Node
ComfyUI Node

MindMap Link Node

The labeled URL brick your ComfyUI mind map is built from

By MrAlgion·Created 5 months ago·Updated 5 months ago· 1
MindMap Link Node
  • info_in
  • INFO_MAP
title
urlhttps://

MindMap Link Node looks pointless until you've tried to keep a big ComfyUI workflow readable. It's a box with a title and a URL. That's the whole thing. But it's the building block of the comfyui_mindmap pack, which exists for one purpose: building a mind map - a knowledge graph - inside your workflow, right next to the graph that's actually making images.

This is deliberately not an image node. It's part of ComfyUI's plumbing layer, the same family as the core Note node and Bjornulf's Note: documentation nodes that never touch a pixel but make a graph legible. Comfy's own Note is just a sticky label, and Bjornulf's added an input and an output so you could wire up simple graphs. These MindMap nodes take that idea and run with it. The author was inspired by a whiteboard-style map from myaiforce.com and basically ported it into the node editor.

What it does

Two text fields in, one socket out:

  • title - the label that sits on the node. Keep it short, like a chapter heading.
  • url - defaults to https://, which is the pack's way of telling you to type over it.

The output is an INFO_MAP, a small dict holding {"title": ..., "url": ...}. Nothing fancy, and that's the point. The more interesting part is the optional info_in socket. Wire one MindMap node's output into the next node's info_in and you get a clean chain - and one node's output can fan out to five branches, which is exactly what the example workflow in the repo does. The mind map is literally the graph you draw: boxes are the nodes, wires are the connections.

One honest gotcha before you build a giant tree: info_in is accepted but not merged into the output. The source returns only the node's own record. The socket exists to give ComfyUI an ordering dependency and to give you a way to draw the structure - so don't expect a node to carry its whole ancestry down the line. The tree lives in the wires, not in the data.

Install

The usual two paths, from the pack's README:

cd ComfyUI/custom_nodes/
git clone https://github.com/MrAlgion/comfyui_mindmap.git

or search "comfyui_mindmap" in ComfyUI Manager. Then install the two Python deps, requests and beautifulsoup4, into ComfyUI's Python environment (venv/conda/portable, whichever you run) and restart. They're almost always already present in a Windows Portable install. The nodes land in a MindMap category.

The honest verdict

If you want a clickable link with a preview, skip this one and grab MindMap Link Node Lite instead - same two fields, but with working Open and Preview buttons. The base node is the plain brick: no buttons, no description. Use it in the middle of a dense map where you want a labeled reference and nothing else. If buttons aren't rendering at all, that's the frontend, not you - the Nodes 2.0 UI rewrite broke a lot of these JavaScript extensions, and toggling back to the legacy canvas is the known workaround.

It doesn't call any external service on its own, needs no API key, and produces nothing you save. It just sits there, holding a URL for you. Some days that's exactly what a 200-node workflow needs.

CategoryMindMap

Inputs (3)

NameTypeDefaultDescription
titleSTRING
urlSTRINGhttps://
info_inoptINFO_MAP

Outputs (1)

NameTypeDescription
INFO_MAPINFO_MAP