Parse JSON String [LP]

This is the mirror image of Modify JSON Object: instead of building a JSON blob field by field, you already have one as raw text - typed in, loaded from a file, or coming back as an API response - and you need it as a structured object the rest of your JSON-typed nodes can actually work with. Parse JSON String does exactly that one job and nothing else.

What it does

Feed it a JSON string and it hands back a parsed json_object. That's the whole node. The obvious pairing in this pack is the Qwen Image Edit API node, whose json_response output is a raw string - run it through Parse JSON String first if you want to work with the response as structured data rather than text you're regex-ing apart by hand.

Inputs and outputs that matter

Just one field:

• json_string (multiline text, defaults to {}) - the text to parse. The empty-object default means the node validates cleanly even before you've wired anything in, which is a small but genuinely useful thing when you're still laying out a graph.

The output is json_object (JSON type), which wires into ModifyJSONObject-LP or anything else that declares a JSON input.

Worth knowing before you rely on it: there's no error-handling widget or fallback value exposed on the node. If what you feed it isn't valid JSON - a trailing comma, an unescaped quote from a model's raw text output - the reasonable assumption is that parsing fails rather than the node silently guessing at what you meant. If you're consuming something you didn't write yourself, like a live API response, it's worth routing the raw string through a Show Text node first just to eyeball it before it hits the parser.

Installing it

Through ComfyUI Manager: search "ComfyUI Level Pixel" or "ComfyUI-LevelPixel." Or clone it directly:

cd ComfyUI/custom_nodes
git clone https://github.com/LevelPixel/ComfyUI-LevelPixel.git

Restart ComfyUI. No models, no extra dependencies - this is plain Python string parsing, same as the rest of the JSON nodes in the pack. They're a recent addition (shipped alongside the Qwen Image Edit API nodes), and the README credits the core JSON logic to Comfyui-Simple-Json-Node rather than claiming it as original work.

Where people get burned

The json_object output only connects to other JSON-typed inputs - this pack's Modify JSON Object node, or any other node that explicitly declares a JSON pin - not to a generic string input. That trips people up the same way the pack's PIPE_LINE type does: it looks like it should snap into anything, and it doesn't.

The other thing worth flagging honestly: this pack's JSON toolkit, as far as the nodes documented here go, covers building an object (Modify JSON Object) and creating one from text (this node), but there's no dedicated "read one field back out" node in what we've covered - no GetJSONValue-style companion. If your workflow needs to pull a single value out of a parsed object and drop it into a widget somewhere (say, an integer from an API response feeding a sampler), you'll likely end up doing that extraction as a string operation rather than through a typed JSON accessor. Keep that in mind before you build a pipeline around deep field access - it may not be a one-node job.