Paged harvest

What it does

Walks one list through its "next page" control, filing every page into the same keyed table.

It runs against one profile, through that profile's own proxy and with its own cookies — so the pages load the way that account's owner would see them. It navigates, so give it a profile whose session you are happy to have in use.

The 9 steps

The real tree, read out of the pack the launcher ships. Indentation is nesting: the steps under a loop run once per row, and the ones under a branch run only when the condition above them holds. Every {{…}} is a value filled in at run time — from the row being walked, from a setting on the run, or from the profile itself.

Each of those is one of the step types on the automation reference, with the same fields the editor shows and the same fields an agent is handed over the local API.

The tables it uses

These load with the recipe. A dataset is a typed table your workspace owns — the columns are named and typed up front so the steps can address them, and every one of them is yours to rename, extend or fill from a file afterwards.

Re-running updates the row it already wrote rather than adding a second one. That is what the match column in the save step is for, and it is the difference between a status check and a table that doubles in size every pass.

What it asks you for

Settings are filled in when the run starts, and every profile can hold its own values — which is how one workflow serves a whole folder of accounts.

start_url

First page · text · required

The list's own first page, as you reach it while signed in. Nothing is stored: the run uses the session, proxy and fingerprint already in this profile.

source

Source name · text · required

Written into every collected row, and half of its key — so two lists never overwrite each other's rows for a page they both link to.

row_selector

Row selector · text

A CSS selector matching ONE item. The default fits an ordinary table or list; a virtualised list draws only what is on screen and needs its own.

next_selector

Next-page control · text

What the run clicks to advance. Many sites label it instead — a link whose text is "Next", or a button with an aria-label. When it stops matching the walk simply ends, so a wrong value here looks like a very short run.

Loading it

In the launcher, open Automations, choose Load a starter pack, and pick Web scraping. Untick anything you do not want. The tables land first, then the workflows, then a project called Collection that links them together.

What arrives is an ordinary automation row. Open it in the editor, change a step, rename it, delete it — nothing in the app treats it as special afterwards, and loading the pack a second time makes a fresh copy rather than overwriting the one you edited. Tables are the opposite: an existing table of the same name is reused and keeps its rows.