Network

HTTP Request Block

HTTP Request sends a configured request and stores status, headers, body, and parsed JSON when available.

At a glance

Methods

GET, POST, PUT, PATCH, DELETE

Output

Response object

Limits

Run/request size limits apply

Error handle

Yes

What it does

HTTP Request connects Scrapeer to external APIs after browser or data Blocks have produced input values.

It supports headers, body modes, content type, timeout, and optional fail-on-HTTP-error behavior.

Use it when

Send scraped data to an internal API.
Fetch additional JSON for a Flow.
Trigger a webhook or external service.

Do not use it when

You need to interact with a browser page; use browser action Blocks.
The target is a private network address blocked by Scrapeer safety checks.
The response body is too large for run limits.

Settings

HTTP Request needs method, URL, headers/body as needed, timeout, fail-on-error behavior, and output variable.

Method and URL

Required: Yes

Variables: URL accepts variables
Description: HTTP method and request URL.

Headers

Required: No

Variables: Yes
Description: Request headers.

Body

Required: Depends on method

Variables: Yes
Description: Request body in the selected body mode and content type.

Timeout

Required: No

Variables: No
Description: Request timeout, capped by runtime limits.

Output variable

Required: Yes

Variables: Variable name
Description: Stores the response object.

Setting	Required	Variables	Description
Method and URL	Yes	URL accepts variables	HTTP method and request URL.
Headers	No	Yes	Request headers.
Body	Depends on method	Yes	Request body in the selected body mode and content type.
Timeout	No	No	Request timeout, capped by runtime limits.
Output variable	Yes	Variable name	Stores the response object.

Outputs

HTTP Request stores the response object.

{{outputVariableName}}object

Response object with statusCode, ok, headers, body, and optional json.

jsonobject | array

Parsed JSON when the response can be parsed as JSON.

Example Flow

Use HTTP Request after collecting data or before a browser step needs API-provided input.

Create or extract request values.
Call the API.
Use the response variable in later Blocks.

Errors and fixes

Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.

The request fails for a private address.

Check: Check whether the URL targets local or private network ranges.
Fix: Use a public endpoint or approved integration path.

The Flow fails on a non-2xx response.

Check: Check fail-on-HTTP-error setting.
Fix: Disable fail-on-error if the Flow should handle status codes manually.

Symptom	Check	Fix
The request fails for a private address.	Check whether the URL targets local or private network ranges.	Use a public endpoint or approved integration path.
The Flow fails on a non-2xx response.	Check fail-on-HTTP-error setting.	Disable fail-on-error if the Flow should handle status codes manually.

Local and cloud runs

Runtime limits include request count, body size, response size, redirect limits, timeout caps, and private-network blocking.

Blocks

Understand how Blocks connect and pass state through a Flow.

Runs and outputs

Inspect Block output, errors, and variables after a run.