Load JSON From URL
Pull live JSON into a workflow
- JSON
This node fetches JSON from a web address at runtime and drops it into your graph as a JSON value you can pick apart. It's the front door for the whole ArtVenture JSON toolkit: LoadJsonFromUrl brings the data in, then GetTextFromJson, GetObjectFromJson and friends dig out the pieces you need. On its own it's just a fetch; paired with those, it turns an external source into live workflow parameters.
Why you'd want it: to make a workflow that reads its settings from somewhere else. Point it at an API that returns prompts, at a config file you host, at a service that hands back generation parameters, and the graph pulls fresh values every run instead of using whatever you typed in last week. It's the difference between a workflow that does one fixed thing and one that does what the data tells it.
How it works
It makes an HTTP request to the URL, expects JSON back, parses it, and outputs the parsed value. Because it parses for you, the output is a real JSON value ready for the Get*FromJson nodes - not a raw string you'd have to decode yourself. The optional console print is a debugging convenience: flip it on and the fetched JSON shows up in your ComfyUI server log so you can see the actual shape and copy the right key paths.
Inputs and outputs
url(required) - the address to fetch from. It must return valid JSON and be reachable from wherever ComfyUI is running.print_to_console(optional, boolean, default false) - dumps the fetched JSON to the server console. Leave it off in production; turn it on when a key isn't matching and you need to see the structure.
The output is JSON - feed it straight into GetTextFromJson (for a string), GetObjectFromJson (to drill into a sub-object), or the other extractors.
Installing it
Comes with the ArtVenture pack. ComfyUI Manager: search comfyui-art-venture, install, restart. Manual:
cd ComfyUI/custom_nodes
git clone https://github.com/sipherxyz/comfyui-art-venture
Restart ComfyUI. No model download; it's a networking node.
Common issues
The request fails or times out. The URL has to be reachable from the machine running ComfyUI, which matters a lot on a cloud or serverless runner - localhost and private LAN addresses won't resolve out there. Use a publicly reachable URL, and confirm it responds in a browser first.
"Not valid JSON" errors. The endpoint returned HTML, an error page, or plain text instead of JSON. A login wall, a redirect, or a rate-limit page all look like "not JSON" to the parser. Check what the URL actually returns - print_to_console or a quick browser hit tells you fast.
Downstream keys don't match. Turn on print_to_console, read the real structure in the log, and copy the exact path into your Get*FromJson node. Guessing the shape is the single most common way this chain breaks.
Auth-protected endpoints. This node fetches a plain URL. If your API needs custom headers or a bearer token beyond what fits in the URL, this isn't the tool - you'd want an endpoint that accepts the key as a query parameter, or a different fetch node.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| url | STRING | — | |
| print_to_consoleopt | BOOLEAN | false | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| JSON | JSON | — |