ceven

Browserless

Runs headless browser scripts to extract dynamic web data, capture page visuals, and bypass bot protections to feed live web content into your workflows.

Try Browserless in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Browserless integration

    • Describe the outcome and Ceven picks the right Browserless calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Browserless data, across all 7 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Browserless access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Browserless, when, and on whose behalf.
    • The agent pauses and asks when Browserless is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Browserless.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Browserless action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Browserless, and when to use it.

Fetch HTML
Pull the full HTML content of a page, including content rendered by JavaScript. Use this for general page analysis.
Scrape with selectors
Extract specific text or attributes from a page using CSS selectors. Use this to build structured lists from web pages.
Take screenshot
Capture a PNG or JPEG image of a webpage. Use this for visual regression testing or archiving page states.
Generate PDF
Convert a webpage into a PDF document. Use this to save invoices, receipts, or reports found on the web.
Unblock content
Access pages that use bot protection or CAPTCHA. Use this when standard fetch requests return a 403 or a challenge page.
Execute custom script
Run a custom Puppeteer script via HTTP. Use this for complex multi step interactions like clicking buttons or filling forms.
Download browser file
Retrieve a file that was downloaded during a browser session. Use this to capture exported CSVs or generated docs.
Get page title
Pull only the title tag of a webpage. Use this for quick page validation before running a heavy scrape.
Check link status
Verify if a URL returns a successful response code. Use this to find broken links on a site.
Wait for selector
Pause execution until a specific element appears on the page. Use this for slow loading single page apps.
Set viewport size
Change the browser window dimensions. Use this to test mobile vs desktop layouts.
Clear browser cache
Reset the session state to ensure a fresh page load. Use this to avoid cached content during testing.
Download file using Puppeteer script
This tool allows downloading files that chrome has downloaded during the execution of puppeteer code. it sets up a blank page, creates a fresh download directory, injects the provided code, and executes it. once the script finishes, any dow
Execute Custom Function
A tool that allows executing custom puppeteer scripts via http requests. this endpoint enables users to run browser automation tasks without managing their own infrastructure.
Fetch HTML Content
This tool fetches the complete html content of a webpage using browserless's content api. it's designed to retrieve the full html contents of any website, including dynamically generated content.
Generate PDF from webpage
This tool generates a pdf from a specified webpage using browserless's pdf generation api. it allows specifying the url of the webpage along with parameters such as format, filename, and waituntil options to control the pdf generation proce
Scrape webpage content using CSS selectors
A tool to extract structured content from a webpage by specifying css selectors. the tool navigates to the specified url, waits for the page to load (including parsing and executing javascript), and returns the selected elements in a struct
Unblock Protected Content
This tool provides access to content from websites that implement bot protection mechanisms. it is designed to bypass various types of protection (such as captcha and bot detections) and return the html content of the protected webpage, wit

18 actions · scroll to see them all

Frequently asked questions

Ceven uses Browserless to launch a full headless Chrome instance rather than just making a simple HTTP request. This means the browser actually executes the JavaScript on the page, runs the scripts, and waits for the DOM to stabilize. You can specify wait conditions in your workflow, telling the agent to wait for a specific CSS selector to appear before it attempts to scrape the data. This ensures that you get the final rendered state of the page, including content loaded via AJAX or React, which traditional scrapers usually miss entirely.
Yes. Ceven leverages the Browserless unblocker feature which rotates proxies and mimics real human browser fingerprints. This includes rotating user agents and handling the TLS handshake in a way that looks like a standard consumer browser. When the agent detects a block or a CAPTCHA, it can automatically reroute the request through the unblocker endpoint. This significantly increases the success rate for scraping sites that actively try to block headless browsers or automated scripts, though some extremely high security sites may still require manual proxy configuration.
Browserless imposes a maximum execution time for each session to prevent runaway scripts from consuming all resources. Depending on your Browserless plan, a script that runs longer than the allotted timeout will be killed by the server. If you are running a very heavy Puppeteer script that performs dozens of page navigations, you might hit these limits. To solve this, we recommend breaking long tasks into smaller, discrete workflow steps. This allows the agent to save state in a database between calls and restart a fresh browser session for each sub task.
The PDF tool in Browserless uses the Chrome Print to PDF functionality, meaning it renders the page exactly as Chrome would if you pressed Ctrl P. It supports custom page formats, margins, and the waituntil parameter, which ensures the PDF is not generated until the network is idle. If a site has a specific print stylesheet, Chrome will honor that by default. You can use custom Puppeteer scripts via Ceven to hide specific elements like nav bars or footers before triggering the PDF print to get a cleaner document.
The limit is determined by your Browserless concurrency settings. If you have a plan that allows five concurrent sessions, and your Ceven workflow tries to launch ten browsers at the exact same second, the Browserless API will return a 429 rate limit error for the excess requests. Ceven handles this by implementing an exponential backoff retry logic, meaning it will queue the failed requests and try them again after a short delay. For very high volume needs, you should increase your concurrency limit in the Browserless dashboard to avoid latency.
Absolutely. While the simple fetch and scrape tools are for read only tasks, the Execute Custom Function tool allows you to send full Puppeteer scripts. This means the agent can click buttons, type text into input fields, select dropdown options, and navigate through a multi step checkout or login flow. You can define the sequence of actions in the script and then have the agent return the final HTML or a screenshot of the result. This makes Browserless a powerful tool for end to end browser automation beyond simple scraping.
When a script triggers a file download in Browserless, the file is temporarily stored in a fresh download directory on the Browserless server. Ceven uses the Download file tool to fetch that file from the server and bring it into your workflow context. Because these directories are ephemeral and deleted once the session ends, the agent must retrieve the file immediately after the download completes. If the session closes before the file is pulled, the data is lost and the script must be run again to regenerate the file.
Yes, you can pass cookies or local storage state into your Browserless requests. When using custom scripts, you can use the Puppeteer API to set cookies before navigating to a page. This allows the agent to act on behalf of a logged in user. However, be aware that some sites use short lived session tokens or multi factor authentication that can invalidate these cookies quickly. For these cases, it is often better to have the agent perform the login flow as part of the script using stored credentials provided securely via Ceven environment variables.

Alternatives to Browserless

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Bright Data logoBright DataApify logoApifyZyte logoZyte

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Browserless and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free