Comflowy Preview JSON

The Comflowy pack is full of nodes that return structured JSON - Comflowy Http Request pulls data from the internet, Comflowy Omost Preview hands back canvas data, and any API-shaped output can carry a JSON payload. The problem: raw JSON in a graph is opaque. You can't see what you got, and you can't tell whether it's what you wanted. Comflowy Preview JSON is the eyeball node for that: it takes a JSON value and renders it as a readable, indented string you can actually read in the UI.

It sounds trivial until you need it. If you've ever wired up an HTTP request, gotten a response that might be "success" or might be an error object, and had no idea which, you know exactly why this node exists. It's the debugging companion that turns "inspect the JSON" from a console-hunting exercise into a one-node glance. And because it outputs a STRING too, it's also a conversion tool: any JSON in, a nicely formatted text representation out, ready to be saved or passed on.

How it works and the inputs

The node serializes the input with json.dumps(..., indent=4) when it's a dict or list, or stringifies it otherwise - then shows the result as a text widget and returns it as a STRING. It's pure formatting; it never touches a network or an API key.

• json_value (required) - any JSON-typed value from the pack or elsewhere.

Output: STRING, the human-readable (indented) representation. The node is marked as an output node, so the pretty text renders in a box right on the canvas.

Installing and the gotchas

Install Comflowy's Custom Nodes via ComfyUI Manager (search "Comflowy") or git clone https://github.com/6174/comflowy-nodes into custom_nodes, restart. No key, no dependencies beyond the pack.

A few honest notes:

• It's a viewer, not a validator. If the JSON is deeply nested, you'll still be reading a lot of text - indentation helps, but this isn't a tree browser. For serious inspection, grab the string output and paste it into a real JSON viewer.
• Order matters for display, not data. The indented output is the same object you fed in; nothing is lost in the round trip. If you're piping the STRING onward, know that you're getting the formatted text, not the original structure.
• Pair it with Extract JSON. The classic pattern is: Preview to see what came back, then Comflowy Extract JSON with the right json_path to pull the one field you actually need.

Small node, zero drama, constant use. Every graph that touches structured data deserves one of these in the corner.