Load JSON From Text

Paste a chunk of JSON, get back a JSON object the rest of Art Venture's JSON nodes can read. On its own it doesn't do much - it parses text into structured data. The point is what comes after: once your parameters live in a JSON object, you pull individual values out of it with the pack's GetTextFromJson, GetIntFromJson, GetFloatFromJson, GetBoolFromJson, and GetObjectFromJson nodes and route them wherever you need.

Why bother? Because it turns a workflow into something you can parameterize from one place. Instead of twelve scattered widgets you tweak by hand, you keep a single JSON blob - prompt, seed, steps, dimensions, whatever - and fan its fields out to the graph. That's especially powerful for API-driven workflows: your app sends one JSON string, this parses it, and the Get-nodes distribute the values. One input, structured, versionable.

How it works

It runs a standard JSON parse over the data string and emits the result as a JSON type. Downstream, the Get-nodes address into it with a key path - the pack uses the format key.[index].subkey.[sub_index], so you can reach nested objects and array elements, e.g. characters.[0].name. Parse once here, then read as many fields as you like.

The inputs and outputs that matter

• data - a multiline string of JSON text. This is where you paste (or wire in) the JSON. It has to be valid JSON - double-quoted keys and strings, no trailing commas, no comments.

Output is a single JSON object. It won't render or preview meaningfully; its job is to travel into the Get-from-JSON nodes.

How to install it

Part of the Art Venture pack. ComfyUI Manager → search comfyui-art-venture → Install → restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sipherxyz/comfyui-art-venture

then pip install -r comfyui-art-venture/requirements.txt and restart. No model download.

Common issues & troubleshooting

It errors on parse. The text isn't valid JSON. The usual culprits: single quotes instead of double, a trailing comma after the last item, unquoted keys, or // comments (JSON has none). Paste your blob into any JSON validator first - this node is only as forgiving as the JSON spec, which is to say not at all.

A Get-node returns nothing. Your key path doesn't match the structure. Remember the addressing format: key.[index].subkey, with array indices in brackets. Print the JSON (there's a print-to-console option on the JSON loaders) or eyeball the structure to get the path right - a mismatched or misspelled key silently yields empty.

Should I use text or URL? This node takes JSON you have as text. If your JSON lives at a URL, the pack's LoadJsonFromUrl fetches it for you instead - same idea, remote source. Use whichever matches where the data comes from.

Node missing after a workflow import. The pack isn't installed - Manager → Install Missing Custom Nodes.