Contexts create
Deprecated compatibility action. Use CREATE_CONTEXT.
ActionTry it
Integrate Browserbase
with your AI CRM
Browserbase is a serverless platform that enables developers to run, manage, and monitor headless browsers at scale, offering seamless integration with tools like Playwright, Puppeteer, and Selenium.
Explore Triggers and Actions
Contexts get
Deprecated compatibility action. Use GET_CONTEXT.
ActionTry it
Create Browser Context
Create a reusable browser context; the API key can select the project.
ActionTry it
Create browser session
Deprecated compatibility action. Use CREATE_SESSION.
ActionTry it
Create Browser Session
Create an isolated Browserbase session and return its connection details.
ActionTry it
Delete a browser context
Tool to delete a browser context and all its stored data (cookies, localStorage, etc.). Use when you need to permanently remove a context.
ActionTry it
Delete a browser extension
Tool to delete an uploaded browser extension by its ID. Use when you need to remove an extension from Browserbase.
ActionTry it
Delete Session Downloads
Tool to delete all file downloads from a specific browser session. Use when you need to clean up session artifacts or free storage space.
ActionTry it
Download Session Artifacts
Download a completed session's generated files as a ZIP archive.
ActionTry it
Get Browser Context
Return metadata for a browser context by ID.
ActionTry it
Get Browser Session
Return status, connection details, and timestamps for a browser session.
ActionTry it
Get Browserbase Project
Return project metadata, default timeout, and assigned concurrency.
ActionTry it
Get project usage statistics
Tool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed. Use when you need to monitor or track resource usage for a specific project.
ActionTry it
Get Session Debug URLs
Return live debugger and WebSocket URLs for a running browser session.
ActionTry it
Get Session Logs
Return network request and response events captured during a browser session.
ActionTry it
Get Session Replay
Return HLS replay metadata and page playlist paths for a recorded session.
ActionTry it
Get Session Replay Page
Return the HLS M3U8 playlist for one recorded replay page. Consume its short-lived signed media URLs promptly rather than storing them.
ActionTry it
List Browser Sessions
List browser sessions, optionally filtered by status or user metadata.
ActionTry it
List Browserbase Projects
List projects with their default timeout and assigned concurrency.
ActionTry it
List Recording Downloads
Poll per-page MP4 assembly after requesting recording downloads until every page is COMPLETED or FAILED. Completed standard-storage pages may include short-lived signed MP4 URLs; BYOS pages may complete without a URL.
ActionTry it
Release Browser Session
Irreversibly request release of a running browser session, ending it before its configured timeout to avoid further charges.
ActionTry it
Request Recording Downloads
Start asynchronous MP4 assembly for every recorded page of a completed session, then poll List Recording Downloads until every page is COMPLETED or FAILED.
ActionTry it
Retrieve a browser extension
Tool to retrieve details of a specific browser extension. Use when you have an extension ID and need its metadata (file name, timestamps, project ID).
ActionTry it
Sessions get
Deprecated compatibility action. Use GET_SESSION.
ActionTry it
Sessions get debug
Deprecated compatibility action. Use GET_SESSION_DEBUG_URLS.
ActionTry it
Sessions get downloads
Deprecated compatibility action. Use DOWNLOAD_SESSION_ARTIFACTS.
ActionTry it
Sessions get logs
Deprecated compatibility action. Use GET_SESSION_LOGS.
ActionTry it
Sessions list
Deprecated compatibility action. Use LIST_SESSIONS.
ActionTry it
Sessions update
Deprecated compatibility action. Use RELEASE_SESSION.
ActionTry it
Update Browser Context
Tool to update a specific browser context. Use when you need fresh upload URL and encryption details for an existing context, after obtaining a valid context ID.
ActionTry it
Upload Browser Extension
Tool to upload a browser extension for use in sessions. Supports Chrome extension format (ZIP). Use when you need to add custom browser extensions to your Browserbase project.
ActionTry it
Upload Session File
Upload one file so browser interactions can select it in a file input field.
ActionTry it
Upload Session Files
Upload multiple files to one browser session for file-input interactions. Each file is attempted independently and the response reports partial failures.
ActionTry it
How the Browserbase integration works
The Browserbase integration connects your Dench AI CRM directly to Browserbase, so agents can read and act on your Browserbase data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
33 actions are available for agents to invoke on your behalf. Every call runs through Browserbase's own authorization, scoped to the account you connect.
Set up Browserbase in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Browserbase and click Connect — you'll authorize access through Browserbase's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Browserbase in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Browserbase integration work with Dench?
The Dench Browserbase integration connects your AI CRM to Browserbase, so AI agents can work with your Browserbase data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with Browserbase via Dench?
The Browserbase integration currently exposes 33 actions, including Contexts create, Contexts get, Create Browser Context, Create browser session, Create Browser Session, and Delete a browser context. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect Browserbase to Dench?
No. You connect Browserbase from your Dench workspace using Browserbase's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the Browserbase integration secure?
Connections are authorized through Browserbase's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Browserbase connection from your workspace settings at any time.