Quickstart
A good first Scrapeer workflow is small: open one page, collect one useful result, run it, and check the output before adding more steps.
What you will build
Start with a workflow that opens a public page and extracts visible information from it. Do not start with a login, CAPTCHA, infinite scroll, or a site that changes heavily between visits. The first run should teach the Scrapeer loop, not every edge case of web scraping.
The workflow has four parts:
- A page to open.
- One or more Blocks that do the browser work.
- An output you can inspect after the run.
- A small change you can make and run again.
Before you start
Pick a page you are allowed to access and automate. If the page requires an account, asks for a CAPTCHA, blocks repeated visits, or hides the data until you interact with it, save that for a later workflow.
For the first run, use the smallest possible example. One page and one extracted value are enough.
Build the Flow
Create or open a Flow in Scrapeer, then add Blocks in the order the browser should act. A typical first Flow opens a URL, waits for the page state you care about, then extracts text or rows from the visible page.
Keep each Block focused. If you need to click a button, add a click Block. If you need to extract repeated rows, use a Block made for repeated data. If you need to reuse a value later, store or reference it with the canonical variable syntax, for example {{variableName}}.
Run and inspect
Run the Flow and watch the browser state. If the Flow fails, fix the earliest Block that did not do what you expected. If the Flow succeeds, inspect the output before adding more pages, loops, exports, or Cloud Runs.
The important habit is simple: build a small Flow, run it, inspect the result, then add the next piece.
Next steps
- Read Flows to understand how execution moves.
- Read Blocks before opening the detailed All Blocks reference.
- Read Variables before passing values between Blocks.
- Use Troubleshooting when a run returns empty data or a browser action fails.