Flows

Flows are browser automation and web scraping tasks broken into visible steps. Each step is a Block, and the connections between Blocks show the order Scrapeer follows during a run.

What a Flow is

A Flow is the saved workflow you build on the canvas. It can open pages, click buttons, fill fields, extract data, transform values, and send output to another destination.

Think of a Flow like a recipe for the browser. Each Block is one instruction. The lines tell Scrapeer what to do next.

Example Flow

A small scraping Flow can open a page, extract repeated data, and log the rows so you can inspect them before adding an export.

This is the shape to look for when you are learning Scrapeer: one Block opens the page, the next Block does the work you care about, and a later Block shows or sends the result. Real Flows can add waits, clicks, loops, exports, and integrations, but the basic reading order stays the same.

How a Flow runs

When you run a Flow, Scrapeer starts at the beginning and follows the connected Blocks. A simple Flow can be linear: open a page, extract data, then save the result. A more advanced Flow can branch, loop over repeated items, or pass values from one Block into another.

Keep the first version linear. Branches, loops, and exports are easier to fix after the basic path works.

What belongs in a Flow

A Flow should contain the browser task, not every possible cleanup step. Put the actions that depend on the website into the Flow: page navigation, clicks, waits, extraction, and the handoff to an output Block or integration.

Use smaller Flows when a job has clear boundaries. A workflow that logs in, searches, extracts a table, enriches each row, downloads files, and sends an email is easier to build when you prove each piece before connecting everything.

What changes between runs