Web Fetch

Fetch data from an HTTP or HTTPS URL with GET, POST, PUT, or DELETE, and extract values with a JSONPath expression.

What it does

Web Fetch calls an HTTP or HTTPS URL and pulls the response into the graph. It sends GET, POST, PUT or DELETE requests, attaches a request body and custom headers, and extracts a single value from a JSON response with a JSONPath expression. Point it at a REST endpoint, a public API, or a local server.

Being a live input, it keeps polling on its own schedule rather than fetching once and stopping. Turn Enabled off to pause it without deleting the node.

When to use it

• Live data from a web API (weather, stock prices, a sensor feed, a webhook payload) brought into the graph

• Parameters driven from a JSON endpoint with a JSONPath, instead of parsing the whole response body by hand

• Data posted out to a server as a side effect of cooking, using POST or PUT with a body

• A health check or status poll, reading Status Code and Success without touching the body

Gotchas

• JSON Path only matters when the response is JSON. Leave it empty for the whole response body as text; fill it in, for example $.data.value, to pull out one field.

• Headers go one per line as Header-Name: value, for API keys (Authorization: Bearer ...) or content-type overrides.

• Check Success and Error before trusting Value or Number. A failed request (timeout, bad URL, non-2xx status) still produces outputs; they just are not meaningful.

Worked example

1. Add a Web Fetch node and paste your endpoint into URL.

2. Leave Method on GET for a simple read. Set JSON Path to something like $.data.temperature to pull just that field out of a JSON response.

3. Raise Poll Interval if you don't need second-by-second updates, which reduces load on the server being fetched from.

4. Wire Number or Value into the rest of your graph, and check Success to gate downstream logic on whether the fetch actually worked.

See also

WebSocket Input · MQTT Subscribe · JSON Import · Numbers, signals & audio