Nodes/ComfyUI-Markmap/Markdown to Mindmap
ComfyUI Node

Markdown to Mindmap

Turn Markdown Into an Interactive Mindmap, Right From Your Workflow

By cenzijing·Created 2 years ago·Updated 2 years ago· 1
Markdown to Mindmap
    • STRING
    markdown_text
    filenamemindmap.html

    ComfyUI is a graph of pixels - most of what you wire together ends in an image or a video. MarkmapNode is one of the few nodes where the output is neither. Give it markdown, and it writes out an actual, interactive mindmap as an HTML file you can open in a browser, zoom around, and share. It's not a visualization of your workflow; it's a tool for organizing content that your workflow already produced - say, structured notes from an LLM node or a plan you typed yourself. If that sounds like a niche, it is. But it's a clean, zero-dependency niche, and when you need it, nothing else in the default node set does it.

    How it works

    The node does the clever part for you: it parses your markdown into a tree - # headings become top-level branches, ##, ### and deeper become nested ones, and lines starting with - become leaf items under the current heading - then inlines that tree as JSON into an HTML template. The template loads the markmap-view and d3 libraries from a CDN, so when you open the file, the browser renders the tree as an interactive mindmap with pan, zoom, and a small toolbar.

    The output is saved to ComfyUI/output/markmap/, and the node hands you back the full path to that file. Two useful details buried in the source: if your first line isn't a heading, it inserts # Mindmap as the root, and if you forget the .html extension on the filename, it appends it for you.

    The inputs that matter

    Only two, and both are in the required list:

    • markdown_text - the multiline string you feed in. Headings and dash-bullets become the mindmap. Everything else gets ignored.
    • filename - defaults to mindmap.html. Just a name; the file always lands in output/markmap/.

    The single output is a STRING: the absolute path of the written HTML file. Wire it into a PreviewText-style node if you want to see the path, or just go grab the file.

    Installing it

    This pack is tiny and has zero Python dependencies - requirements.txt literally says "No additional requirements". No model downloads, no CUDA, no pip step. The real way:

    • ComfyUI Manager → search ComfyUI-Markmap (or "Markmap") → Install → restart.
    • Or manually: cd ComfyUI/custom_nodes && git clone https://github.com/cenzijing/ComfyUI-Markmap, then restart ComfyUI.

    Both nodes land under the markmap category in the menu.

    Where people get burned

    The big one is internet access. The generated HTML renders by pulling d3 and markmap from a CDN, so open it on a machine with no network and you'll get a blank page - the file is fine, the libraries just never loaded. If that's you, consider saving the markdown elsewhere or self-hosting the libs.

    Second gotcha: this is a heading-and-bullet parser, not a full markdown renderer. Plain prose paragraphs between headings are silently dropped, and so are code blocks and tables. Keep your input structured as # / ## / - lines and what you see matches what you wrote.

    Third, a path reality check: the README says the output goes to /root/ComfyUI/output/markmap/mindmap.html. That /root is the author's container. On your machine it's wherever ComfyUI's output folder actually lives - check ComfyUI/output/markmap/.

    It's not a tool you'll use every day. But when you want your LLM's brainstorm as something you can actually click around instead of a wall of # signs, this is the whole job in two inputs.

    Categorymarkmap

    Inputs (2)

    NameTypeDefaultDescription
    markdown_textSTRING
    filenameSTRINGmindmap.html

    Outputs (1)

    NameTypeDescription
    STRINGSTRING