Blocks
Blocks are the steps inside a Scrapeer Flow. One Block does one job: open a page, click an element, extract data, change a value, branch the Flow, or send the result somewhere else.
What Blocks do
Blocks make browser automation editable. Instead of hiding the workflow inside a script, Scrapeer shows each action on the canvas. If a run fails, you can inspect the Block that produced the wrong page state, empty output, or error.
Use the All Blocks reference when you need exact settings, outputs, and fixes for a specific Block.
Example Block
This is the shape of a Scrapeer Block on the canvas. The header tells you what the Block does, the body holds the settings, and the handles around the edge connect it to the rest of the Flow.
This example uses the Extract Data Block because it shows the common Block parts clearly: a title, settings, optional sections, fields, and an output variable. Exact Extract Data behavior belongs in the Extract Data Block reference page.
Settings
Each Block has settings for its own job. A navigation Block needs a destination. A click Block needs the thing to click. An extraction Block needs to know what page content to read. Some settings accept variables, which lets a later Block use a value created earlier in the Flow.
Use the exact labels in the Block page when you configure a Block. Public Block docs should match the app, not a guessed name.
Inputs and outputs
Blocks can receive values from earlier Blocks and produce values for later Blocks. The connection between Blocks controls the execution path. Variables control reusable data.
For example, one Block can extract a product name and another Block can use that value in an email, spreadsheet row, API request, or later browser action. Use {{variableName}} when a setting needs a value from earlier in the Flow.
Choosing the right Block
Pick the Block that matches the browser task. Use a navigation Block to open a page, a click Block to press something, an extraction Block to read page content, and an output or integration Block to send results out of the Flow.
If two Blocks look similar, start with the more direct one. A Flow is easier to debug when each Block has a clear reason to exist.