Skip to main content
Node type: http_request · Version: 1 · Category: Network Call an HTTP endpoint. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Read JSON from an API without opening a browser.
  • Send a bounded JSON request to an approved domain and route on its response.

​
Example: Check a JSON health endpoint

Request an endpoint once, retry one transient failure, then use status and body in later nodes.
Example settings
This shows the important settings, not a complete exported node.
  1. Approve api.example.com during permission review.
  2. Test the node and inspect the actual body shape.
  3. Map status into Condition and selected body fields into later nodes.

​
Configuration

Authorization and cookie values are redacted from execution data.
Retries are capped at 5, timeout is clamped to 100–120000 milliseconds, redirects are limited to 10, and response output is limited to 1 MB.

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

​
Outputs

​
Execution behavior

  • Query object values are encoded into the URL; body is intended for POST, PUT, and PATCH.
  • The output includes the numeric status, decoded body, and final URL after redirects.
  • The editor catalogue declares status (number), body (any), finalUrl (string) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • A non-success HTTP status can still be a valid HTTP response; branch on status when the workflow requires 2xx.
  • Keep retries low for mutating methods unless the endpoint supports idempotency.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.