Scrapeer
Flow control

Start Block

The Start Block is the entry point for every Flow. Every run begins here, then follows the connected output handle into the first real browser or data step.

At a glance

Best for
Beginning every Flow
Required
Exactly one per Flow
Produces variables
No
Error handle
No

What it does

Start marks the first step in a Scrapeer Flow. It does not open a page, click anything, extract data, or create a user variable by itself.

Use it to configure run-level behavior such as pacing and Cloud-oriented browser options, then connect it to the Block that should run first.

Use it when

  • Begin a new Flow before connecting browser actions.
  • Set the run pacing that should apply to the Flow.
  • Configure Cloud-run options that belong to the whole browser session.

Do not use it when

  • You need to open a web page; use Go To URL after Start.
  • You need to define reusable values; use Variables after Start.
  • You are trying to create a second entry point in the same Flow.

Settings

The Start Block settings are run-level settings. They affect how the Flow starts or how the browser session should behave, not a single page action.

Run pacing

Required: No
Variables
No
Description
Controls the general pace of browser actions. The default UI choice is Balanced.

Stealth Mode

Required: No
Variables
No
Description
Cloud-run option for protected sites. It is shown on Start because it belongs to the browser session, not one action Block.

Browser profile

Required: No
Variables
No
Description
Cloud-run browser profile option shown on Start when available for the current Flow.

Outputs

Start does not create a user variable. Later Blocks cannot reference a value from Start with {{variableName}}.

No user variableN/A

The Start Block only moves execution to the next connected Block.

Example Flow

A normal Flow begins with Start, then opens or prepares the page before extraction, clicking, or export Blocks run.

  1. Start the Flow.
  2. Open a page with Go To URL.
  3. Add the next browser or extraction Block.

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 Flow never reaches the first action Block.

Check
Check that the Start output handle is connected to the next Block.
Fix
Connect Start to the first Block that should run.

Cloud browser settings do not appear to affect the run.

Check
Check whether the run was started as a Cloud Run.
Fix
Use a Cloud Run for Cloud-only browser settings such as Stealth Mode.

Local and cloud runs

The Start Block itself is a no-op in both local and cloud runtimes. Run-level options configured on Start can still affect the browser session outside the Block handler.

Go To URL Block

Open the first page after Start.

Blocks

Understand how Blocks connect and pass state through a Flow.

Variables

Use saved values with the canonical {{variableName}} syntax.