Skip to content
All docs
Automation5 min

Scheduled cloud runs

Promote a recipe to a schedule, choose a destination, and set the caps that keep it predictable.

Promote a recipe

Build and test the extraction locally first — always. When the columns are right, open the run menu and choose Promote to cloud. The selectors, pagination settings and transforms all travel with it.

Schedule

Intervals run from every ten minutes to once a month, in the time zone you pick rather than UTC-and-do-the-maths-yourself. Runs that overlap are skipped rather than queued, so a slow run cannot pile up behind itself.

Destinations

A run has to end somewhere useful.

  • Google Sheets: create a new sheet each run, replace the contents of one sheet, or append rows with a run timestamp column.
  • Webhook: a POST of the batch as JSON, with retries and a signature header so you can verify it came from us.
  • Storage: keep the last 30 runs downloadable as CSV from the dashboard.

Guardrails

Set a page cap per run and a monthly cap per account. Set an alert threshold too: if a run returns fewer than N rows, you get an email instead of a sheet full of blanks. That single setting catches almost every case of a site changing its markup underneath you.

$15 · one payment · lifetime

Stop copying tables by hand.

Install the extension, click one row, and watch the rest arrive. If it does not do what you need in the first ten minutes, you have lost nothing.