Browserbase
Browserbase headless browser sessions
Browserbase runs managed headless Chromium sessions on its own infrastructure — built for AI agents and scrape workflows that need a stable browser without the operational headache of managing the runtime. Tiny Command exposes six actions against the session lifecycle: Create Session (returns a session ID, connect URL, and a debug URL), Get Session, List Sessions, Get Debug URL (returns the live VNC-style viewer link for an in-flight session), Get Recording (returns the rrweb-format recording of a completed session for replay), and Close Session (terminates and releases the session slot). There are no triggers — Browserbase is action-only, fitted into workflows that orchestrate scraping or LLM-driven browsing. The connection authenticates with a Browserbase API key at project scope; sessions billed against the project. The typical pattern: Create Session → run Playwright/Puppeteer code against the connect URL (in a Code step or separate process) → Close Session in a finally block to avoid stranded sessions on partial failures.
Do anything Browserbase can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Close Session | Stops a session early and releases the slot. Call this in a workflow's finally block to avoid orphaned sessions consuming slots. Sessions auto-close at the configured timeout (default 60min); explicit close saves cost on short jobs. |
| Create Browser Session | Starts a new headless Chromium session. Returns a session ID, connect URL (for Playwright), and debug URL (live VNC viewer). Optional context_id to reuse a saved auth profile, optional proxies for residential routing. |
| Get Debug URL | Returns the short-lived live-viewer URL for an in-flight session. Open in a browser to watch the headless Chromium in real time — useful for debugging "why did the scrape break" or "what did the agent actually see" mysteries. |
| Get Session Recording | Returns the rrweb-format recording of a completed session. Replay with the rrweb-player library to reconstruct the session's DOM mutations and user input. Useful for after-the-fact debugging of failed runs. |
| Get Session | Returns metadata for a specific session — status, runtime, region, configured proxies. Useful for monitoring active sessions or auditing past runs. |
| List Sessions | Paginated session history with status filters. Useful for "any orphaned sessions still consuming slots?" cleanup or for capacity planning around session quota usage. |
Pre-built Browserbase workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Browserbase once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Browserbase field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Browserbase integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Browserbase to Tiny Command?
What Browserbase triggers does Tiny Command support?
What Browserbase actions can I run from a workflow?
Is the Browserbase integration real-time?
Do I need to write code to use Browserbase with Tiny Command?
How much does the Browserbase integration cost?
More spreadsheets & databases apps people connect.
Same category as Browserbase, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Browserbase.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
