Examples
Ready-to-use starting points. Open one, read how it works, and adapt it to your own task — the same examples ship with Orbe and appear in the launcher gallery.
Code recipes Python
Runnable Python, using only the orbe package and the standard library. See the SDK reference.
Basic login
Open a site and sign in, binding the username and password from variables — never hard-coded.
View recipe →Scrape a list
Scroll through a list and read its items on the browser side (no in-page script).
View recipe →Run a fleet
Run the same task across many profiles at once, each keeping its own behaviour.
View recipe →No-code workflows Workflow Editor
Open these in the Workflow Editor and adapt them — no code needed. Each one demonstrates a different capability.
Health-check a list of accounts
Rotate through a CSV of accounts and check each one is still healthy: log in, confirm the logged-in marker, screenshot the state, and stop that account cleanly on a checkpoint. A quick way to see which accounts survived. Point data.path at your CSV (columns: user, pass); run each in its own Orbe profile. No posting or risky actions — read-only health check.
View workflow →Ask me for the code, then continue
When a step needs a human — a one-time code from your phone, or a captcha answer — pause and ask, then type what you enter and carry on. The machine keeps the flow; you only supply the part a machine shouldn't.
View workflow →Stop and hand off on a captcha
Do the work, but the moment a captcha or verification challenge shows up, stop, screenshot it, and hand control back to you — Orbe never tries to solve or bypass a challenge. Use this pattern in any flow where a checkpoint is likely. Discipline also stops on checkpoints automatically; this makes the hand-off explicit and captures evidence.
View workflow →Post from a CSV list
Run one flow per row of a CSV (for_each_row): open the composer, type the post text from the row, submit. Point data.path at your own CSV with a 'text' column. Pacing keeps it human-paced; a checkpoint stops the whole run.
View workflow →Basic login
Open a site, sign in with credentials bound from variables (never hard-code passwords in a template), stop safely if a verification checkpoint appears.
View workflow →Add to cart and check out
Open a product page, add it to the cart, go to checkout and fill the shipping form, then stop just before payment for you to review. Bind any payment or personal details to variables or a data source — never hard-code them. This template stops before submitting payment on purpose.
View workflow →Fill a multi-field form
Fill a registration or profile form field-by-field (located by each field's visible label — no CSS selectors), then submit and confirm. Bind every value to a variable or a CSV row; never hard-code personal data. To fill one form per row of a CSV, wrap the steps in a For-each-row loop.
View workflow →Log in and confirm the session
Sign in, stop safely if a verification checkpoint appears, then confirm the account is really logged in before doing anything else. Credentials are bound to variables — replace them or load from your own store; never hard-code real passwords.
View workflow →Warm-up browsing
Light, human-paced browsing to warm up a fresh profile: open the feed, scroll a few times with reading pauses. No posting, no risky actions — pacing and the per-profile persona keep it human.
View workflow →Fresh IP for every account
Warm up a list of accounts, rotating to a fresh proxy IP before each one so they never share an IP. The proxy step runs through Orbe's local gateway. Fill accounts.csv with your own logins.
View workflow →Post a run result to your webhook
After doing the work, read the page and POST a short result to your own HTTPS endpoint. The request is SSRF-hardened (https only, internal/private targets refused) and runs only in a trusted workflow — it sends no cookies or credentials of its own. If your endpoint needs an API token, put it in a header through a {{variable}}.
View workflow →Click with a backup selector
Try to click the primary button; if the page changed its label, fall back to a backup label instead of failing the whole run. This is per-block error handling — a resilient pattern for sites that A/B-test their UI.
View workflow →Reuse a snippet with Call-workflow
Open a page, then run the reusable 'accept a cookie banner' snippet as a sub-step before doing the real work — so you write that handling once and call it from every flow. The sub-workflow is resolved locally and always runs at the least-trusted level of caller and callee.
View workflow →Scrape a list, de-duplicate, count
Read the actionable elements on a page, drop duplicates, keep the first ten, and count them — a starting point for any scrape that needs cleaning before export. Extend with your own selectors and a write step (for example, a request to your own webhook).
View workflow →Scrape a paginated list
Load a list page, then keep clicking "Load more" until it disappears (a while-loop), reading the items each round. Point list_url and the button/marker text at your target. Nothing is submitted — this only reads.
View workflow →Snippet: accept a cookie banner
A small reusable snippet — if a cookie banner is showing, accept it; otherwise do nothing. It opens no tab of its own, so other workflows can call it as a first step. Referenced by other templates through the Call-workflow block.
View workflow →Warm up a list of accounts
Run one light warm-up per row of a CSV of accounts: open the feed, scroll and read a few times with human pauses, and stop that account cleanly if a checkpoint appears. Point data.path at your CSV (columns: user, pass). Pacing and each profile's own persona keep it human; run each account in its own Orbe profile.
View workflow →Resume a multi-day warm-up
Remember which day of a warm-up schedule this profile is on across separate runs, do that day's browsing, then advance the counter. State persists between runs, so a crash or an overnight gap doesn't restart the schedule.
View workflow →Build your own: Workflow Editor · Blocks & Actions · SDK & MCP.