Schedules
Hourly, daily or weekly, in your timezone. Each finished run becomes a new version of the table, so you keep the history instead of overwriting it.
Cloud
For the runs that should happen while you sleep
The extension needs your browser to be open, and a weekly price check should not have to wait for that. Save the recipe once, hand it to the server and read the table in the morning.
Cloud runs are not switched on yet. This page describes what the server side will do and the limits it will carry, so you can judge now whether it fits. The extension works today and MCP works today on a Pro account. Cloud runs will belong to Pro+ when they exist.
What it will do
Webhook
A POST to your address when a run finishes, with the run id, the status and the row count. Enough to trigger an import on your side.
Run history
Status, duration, pages visited, rows written and the full log for every run, including the ones that stopped at a verification page.
Long URL lists
Page extractor jobs over thousands of addresses, kept inside the same per host budget as a run in your browser.
What the cloud cannot do
Most tools keep this part in a support article. We would rather you read it before you plan anything around the cloud.
- One server, one datacenter address, in Germany. Every cloud run leaves from the same IP range.
- There is no proxy pool, no residential addresses and no country selector, because we are not reselling somebody else's traffic.
- The cloud has no login sessions, so it sees what a signed out visitor sees. Pages behind your account belong in the extension.
- Sites that block datacenter traffic outright will block it here too, which is the trade for a run that happens while you are away.
Which one to use
Run in the browser when the page needs your session, when the site is strict, or when you want to watch the first run and fix a column.
Chrome extensionRun in the cloud when the source is public, the list is long and the job repeats on a schedule.
Pricing