Scrapeer Documentation

Scrapeer helps you build browser automation and web scraping workflows with visual Blocks. This documentation explains how Flows work, how values move between Blocks, how runs produce output, and where to look when a workflow breaks.

What Scrapeer documentation covers

Use this documentation when you want to understand Scrapeer before signing in, build a first browser workflow, or check exact Block behavior while working in the app. The public documentation stays focused on product behavior: what you can configure, what you can see during a run, what output you get, and what to fix when the page does not behave as expected.

Internal architecture notes, deployment details, and private debugging plans do not belong here. If a detail does not help you decide, configure, run, or repair a Flow, it stays out of the public docs.

Start with the product model

A Flow is the full browser job. A Block is one step in that job: open a page, click something, extract data, transform a value, or send the result somewhere else. Lines between Blocks show how execution moves from one step to the next.

Start with Flows and Blocks if you are new to Scrapeer. Open Variables when you need to reuse a value later in the Flow, and Runs and outputs when you want to understand what happened after pressing run.

Documentation areas

The docs are grouped by the way you work: learn the model, build a small workflow, look up a Block, then troubleshoot the run.