Running Cloud Tasks: The Run in Cloud Wizard
Send a tested local extraction to a cloud browser with the Run in Cloud wizard — pick an automation, configure proxies and integrations, then run.
Cloud tasks are created from the extension's side panel with a two-step Run in Cloud wizard. You hand a working local extraction to a cloud browser, tune how it should run, and launch it.
Open the wizard from the Run in Cloud card on the side panel home screen, or from the cloud button inside a supported tool.
Step 1 — Select an automation
You pick a previously-run local automation from your history. The list shows your past runs, filtered to the cloud-supported task types: List Extractor, Page Extractor (including Google Maps mode), Email Extractor, and Social Link Extractor.
There is no URL box
The wizard intentionally has no free-form URL input. You configure and test the extraction locally first — where iteration is free and instant — then send the proven setup to the cloud. If you haven't run anything yet, two demo automations are available so you can try the flow.
Step 2 — Configure
The configure screen shows a preview card for the selected automation, the schedule picker, and expandable configuration groups:
| Group | What it controls | Default |
|---|---|---|
| Automation | The extraction itself: URLs, selectors, pagination | As tested locally |
| Page Unblocker | Captcha and block handling (details) | — |
| Integrations | Google Sheets and webhook exports | Off |
| Browser Location | ISP or residential proxy, country/city | ISP, random location |
| User Agent & Viewport | Device presets | Your current browser |
| Data Cleanup | Remove empty, duplicate, sparse, and repeating rows and columns | On |
| Cookies & Storage | Clone your session into the cloud browser | Off |
The defaults are sensible: most tasks only need a schedule, and perhaps a proxy location or a Sheets export.
Launch
Submit with Run Now (one-off) or Run & Schedule (recurring). Either way, the task always runs immediately on creation — a scheduled task doesn't wait for its first slot, so you can verify it works right away.
The success screen links to the dashboard, where you'll see the run's timeline and its results table as rows come in. Each page the cloud browser extracts consumes one credit.