All Blocks
Blocks are the visible steps you connect to build a Scrapeer Flow. Use this index when you know the browser task you want to automate and need the right Block for it.
Browse Blocks
Start with the category that matches the job: browser actions, extraction, flow control, outputs, or integrations. Individual Block pages explain what the Block does, when to use it, settings, outputs, example Flows, and fixes.
Block pages must match the product. If a setting, output, handle, error, or Cloud Run behavior changes, the matching page needs to change with it.
Public Block reference
VerifiedThe reference catalog covers public Scrapeer Blocks with source-checked behavior, settings, outputs, and runtime caveats.
Block handles
Most Blocks have an incoming handle on the left and a main output handle on the right. Execution enters through the incoming handle, then continues through the main output when the Block succeeds.
Blocks that can fail also have an error handle. Connect it when the Flow should recover, log the problem, or run a fallback path. If the error handle is not connected, a failure stops that path.
Before opening a Block page
If you are new to Scrapeer, read Blocks first. If you already know what a Block is, use the reference while building:
- Check whether the Block matches the browser action you need.
- Read the setting table before changing defaults.
- Check which output values later Blocks can use.
- Use the example Flow to understand where the Block usually sits.
- Start troubleshooting with the earliest Block that produced the wrong state.