Browserless is a service that provides headless browser automation, allowing users to run automations on their own sites with browser infrastructure.
Browserless is a service that provides headless browser automation, allowing users to run automations on their own sites with browser infrastructure. On Nagent, Browserless is exposed as a fully-configurable developer tools integration that any agent can call — 7 actions, and API key authentication. No code is required to wire Browserless into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Browserless to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Browserless into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Browserless, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BROWSERLESS_DOWNLOAD_FILEThis 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 downloaded files from Chromium are returned with the appropriate content-type header.
Input parameters
The Puppeteer script to execute for downloading the file. This should be a valid JavaScript code that triggers a file download.
Additional context data to be passed to the script
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERLESS_EXECUTE_CUSTOM_FUNCTIONA tool that allows executing custom Puppeteer scripts via HTTP requests. This endpoint enables users to run browser automation tasks without managing their own infrastructure.
Input parameters
The Puppeteer function code to execute. Must be a valid ESM module with a default export function.
Optional context object to pass to the function. Supports any JSON-serializable nested data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERLESS_FETCH_HTML_CONTENTThis 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.
Input parameters
The URL of the webpage to fetch HTML content from
Whether to continue on error
Navigation options like waitUntil
Wait for specific event with optional timeout
Wait for specific time in milliseconds
Wait for specific element with optional timeout
Types of resources to block (e.g., images, stylesheets)
Patterns to block specific requests
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERLESS_GENERATE_PDFThis 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 process.
Input parameters
URL of the webpage to generate PDF from
HTML content to generate PDF from
PDF generation options based on Puppeteer's PDFOptions.
Custom style tags to inject
Continue on error
Navigation options for page loading.
Custom script tags to inject
Options for waiting for a selector to appear.
Resource types to block
Request patterns to block
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERLESS_SCRAPE_CONTENTA 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 structured JSON format.
Input parameters
The URL to scrape content from
Array of objects containing CSS selectors to extract
Options for page navigation
Wait for a specific event to occur
Wait specified milliseconds before scraping
Wait for a custom JavaScript function to return true
Wait for a specific selector to appear
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERLESS_TAKE_SCREENSHOTA tool that captures a screenshot of a webpage using browserless's screenshot API. The tool takes a URL and returns either a PNG or JPEG image. It includes options for full page capture, image type, quality, and clipping coordinates.
Input parameters
The URL of the webpage to capture
X coordinate for clipping the screenshot
Y coordinate for clipping the screenshot
The quality of the image (0-100, only applies to jpeg)
Whether to capture the full page or just the viewport
Width of the clipping area
The type of image to return (png or jpeg)
Height of the clipping area
Whether to omit the background in the screenshot
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BROWSERLESS_UNBLOCK_PROTECTED_CONTENTThis 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, with optional customization through parameters like waitFor, timeout, and stealth mode.
Input parameters
Time to live for the browser instance in milliseconds
The URL of the protected webpage to access
Whether to return the HTML content of the page
Whether to return cookies from the page
Whether to return a screenshot of the page
Event to wait for before returning the response
Function to execute and wait for before returning the response
Selector to wait for before returning the response
Whether to return a WebSocket endpoint for browser automation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 51 agents privately built on Nagent that already use Browserless.
Build on Nagent
Connect Browserless to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Browserless, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Browserless is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Browserless is connected, you configure its 7 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Browserless steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Browserless event fires, the agent kicks off automatically.
Every Browserless action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Browserless ships with 7 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Browserless together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Browserless-based workflows tailored to your business.