Web fetch
Fetch a URL · call an API
Web fetch reaches out to a web address in the middle of a running job, either to load a page or to call another service, so your flow can look something up or pull in data from an outside system as it works.
How it works
Sometimes a workflow needs a fact it does not already have in front of it: a current rate, a status from another system, a detail sitting on a web page. Web fetch is the node that goes and gets it. It contacts the address you give it, mid-flow, and brings the response back into the job.
That response then becomes something the next steps can use. You might fetch a record from another company's system to confirm a detail, or call a service to enrich what you already have before a report is written. The fetched data joins the job like any other input.
Think of it as the workflow's window to the outside world. Most nodes work only with what came in at the start, but this one lets a job pause, ask an external source a question, and act on the answer.
Common use cases
Real situations where this node earns its place in a flow.
Call an API mid-flow
Fetch data from an external service to add to a job, such as a lookup, a rate, or a status.
Pull a webpage to watch
Retrieve a page and pair it with a change gate to act when its content moves.
Reach any HTTP endpoint
Call a system that has no dedicated node by hitting its API directly.
Web fetch in a workflow
A simple example of where this node sits in a flow.
What you set up
- Enter the web address (URL) the node should contact.
- If the service needs a key or sign-in, provide those credentials so the request is accepted.
- Decide what the flow should do with the response, since the next steps run on what comes back.
Common questions
Can it reach a service that requires a password or API key?
Yes. You supply the credentials the service expects, and the node includes them so the request goes through, rather than being turned away.
What is the difference between this and the outbound webhook?
Web fetch reaches out to get something back and use it in the flow. Webhook out is about pushing your result to another system, not pulling data in.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
urlreqURL to fetch; supports {token} substitution from job state; no-ops if blank.
Type: stringmethodHTTP method for the request; invalid values fall back to GET.
Type: enum: GET | POST | PUT | DELETEDefault:GETheadersRequest headers as a JSON object; malformed JSON is ignored.
Type: JSON stringbodyRequest payload, sent for non-GET methods only.
Type: stringauthTokenBearer token (or secret ref) sent as an Authorization header.
Type: stringoutputsComma-separated response parts to expose downstream (status, headers, html, text, meta).
Type: stringDefault:status,headers,textextractModeHow to extract a single value from the response body.
Type: enum: json-path | regexextractExprThe JSON dotted path or regex used to extract the value when extractMode is set.
Type: stringtimeoutMsRequest timeout in milliseconds.
Type: numberDefault:30000coalesceCoalesce identical public GETs fleet-wide so the URL is fetched once and fanned out.
Type: booleanDefault:true
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "web-fetch",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "web-fetch",
"kind": "processor",
"title": "Web fetch",
"subtitle": "Fetch a URL · call an API",
"config": {
"url": "",
"method": "GET",
"headers": "[]",
"body": "",
"authToken": "",
"outputs": "status,headers,text",
"extractMode": "json-path",
"extractExpr": "",
"timeoutMs": "30000",
"coalesce": "true"
}
}
}