Connect Browserless integrations
VerifiedRender pages to PDFs and screenshots, scrape sites and run crawls in cloud browsers, connected to WEXTL workflows and AI agents. Replace glue scripts around Browserless with visual workflows. Start from Get a Batch Scrape, then run Get a Crawl or Get a Profile.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Browserless integration
Triggers can detect changes in Browserless and run actions that can create, search or modify data inside Browserless automatically[3], exactly how you set them.
- Get a Batch Scrape Reports the Status, Total Pages, Completed Pages and Failed Pages of a batch scrape. Use Skip to move past results already read.
- Get a Crawl Checks on a crawl and reports its Status and how many Completed Pages it has. Use Skip with the Next Page URL from the previous answer to read further pages.
- Get a Profile Shows one saved browser profile, with its Name, its Cookies and Origins, and when it was Last Used.
- Get a Profile State Exports the saved Cookies and the Origins for one profile. Because the reply contains session cookies, keep it out of logs.
- Get an Agent Run Reads the Status, Result and Steps of an AI browser agent run, including any Error. Use Max Response Size (bytes) to limit how much is returned.
- Get Page Content Loads a Page URL, or HTML of your own, and returns the resulting HTML. Use Wait for Selector to hold until an element appears, and Cookies to open a page with cookies already set.
- Get the Service Info Reports the Version of Browserless along with the browser builds it runs: Chromium, WebKit, Firefox, Playwright and Puppeteer.
- List Agent Runs Shows agent runs, each with its Run ID, Status and a Preview. Use Status to list runs that are in one state.
- List Crawls Returns crawls with their URL, Status and Total Pages. Narrow the list to one Status, or lower Limit to return fewer crawls.
- List Profiles Retrieves saved browser profiles with Name, Domain Auth and Last Used. Use Limit to restrict how many are read.
- List Proxy Cities Finds the countries and cities where city-level proxying is available. Use Country to look at a single country, and read Total Cities for the count.
- List Scrapers Returns the ready-made scrapers Browserless provides, together with a Version number.
- List Site Skills Lists the skills saved for one Domain, each with its Title and Version. Use Task to narrow them to a particular job.
- List Website URLs Maps a site to its page URLs, returning URLs and a Count. Use Search to filter the URLs by text, and Sitemap to include, skip or use only the sitemap.
- Search the Web Runs a web search for a Query and returns Web Results, News Results or Image Results. Use Scrape Results As to fetch the content of each hit.
- Audit Page Performance Runs a Lighthouse audit on a Page URL and returns the Lighthouse Report. Use Categories to pick which scores to compute and Budgets to set performance limits.
- Cancel a Batch Scrape Halts a multi-URL scrape that is still underway.
- Cancel a Crawl Ends a site crawl that is in progress. A crawl that has finished cannot be cancelled.
- Cancel an Agent Run Stops an agent run that is still active. A run that has already finished is deleted instead, together with its result.
- Create a PDF Renders a Page URL or your own HTML to a PDF file. Set the Paper Format and Margin Top, switch to Landscape, or give Page Ranges to print only some pages.
- Create a Session Starts a persistent browser that is billed while open and closes after the Time to Live (ms). Add a Profile to reuse saved logins, or a Start URL to open a page right away.
- Delete a Profile Deletes a saved browser profile along with its stored logins and cookies, and returns its Name with a Deleted flag.
- Delete a Session Stops a running browser session. Turn on Force to end it even when it is busy.
- Download Files Runs your Puppeteer JavaScript Code, which should click a download link, and returns the File the browser downloaded. Use Context for values the script reads.
- Export a Page Saves a page as a file from its Page URL. Turn on Include Resources to get a zip with its images, scripts and styles.
- Make an API Call Calls the Browserless REST API directly with a free-form request under your saved credential.
- Run a BrowserQL Query Executes a BrowserQL GraphQL document that drives a cloud browser and returns its Data or Errors. Pass Variables to parameterise the Query.
- Run a Function Runs your Puppeteer JavaScript in a cloud browser and returns its Result with the Content Type. Use Context to feed variables to the code.
- Run a Scraper Calls one of the ready-made scrapers listed by List Scrapers, such as google. Use Parameters to pass the inputs its API expects.
- Scrape a Page Extracts a page through Browserless smart scrape. Use Formats to choose Markdown, HTML or Links, and turn on Only Main Content to skip menus and footers.
- Scrape Page Elements Reads the text, HTML and attributes of everything that matches the CSS selectors. Add selectors to Elements and point at a Page URL, or feed markup through HTML.
- Start a Batch Scrape Queues an asynchronous scrape of many URLs. Turn on Skip Invalid URLs to ignore bad entries and use Webhook URL to be told when it ends.
- Start a Crawl Begins an asynchronous crawl of a site from a Start URL. Use Page Limit and Max Depth to bound it, and Include Paths or Exclude Paths to steer it.
- Start an Agent Run Launches an AI browser agent on a Task, optionally from a Start URL. Use Max Steps to cap its work. The reply gives a Run ID and Status.
- Take a Screenshot Renders a Page URL or HTML to an image file. Use Selector to capture one element, Full Page for the whole scroll height, and Image Type for the format.
- Unblock a Page Loads a page protected by bot detection and returns its HTML, Cookies or a Screenshot (Base64). Turn on Keep Browser Open to keep working in the same browser.
- Update a Profile Name Renames a saved browser profile to a New Name. A name that another profile already uses is rejected.
- Update a Profile State Replaces the stored Cookies and Origins of a profile by supplying a new State, a JSON object shaped like an export of the same profile.
- Upload a Profile Makes a new browser profile out of a Name and a State of cookies and origins. Returns the Profile ID.
How to integrate Browserless in automation workflow?
Browserless in three steps: start with "Get a Batch Scrape", connect one credential, then add your next step.
STEP 1
Select Browserless in workflow
Add the "Get a Batch Scrape" action from Browserless to the canvas[4].
STEP 2
Connect Browserless
Fill in the Browserless credential once. All 38 Browserless modules use it[3].
STEP 3
Build a workflow
Add "Get a Crawl" or "Get a Profile" after it, then connect any app[5] or the HTTP node.
How Browserless connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Browserless app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Browserless supports.
Full Browserless API documentationThe following table illustrates what fields Browserless integration require during authorization flow inside our workflow builder[4].
Connect Browserless
API Token*Text
••••••••
Region*Text
••••••••
| Field | Type | Help |
|---|---|---|
API TokenRequired | password | In the account dashboard, open API Keys and copy the API token. |
RegionRequired | select | The region your account uses. |
| Custom Host | text | Only for a private Browserless deployment. Host name only: no https://, no path, no trailing slash. It must be reachable over https. Leave blank to use the Region. |
Connect Browserless to popular apps on WEXTL
Enter a name of the other app you want to sync with Browserless below. Click on selected app to explore integration options with Browserless. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Browserless integration
Select Get a Batch Scrape action from Browserless - this will be a starting point in your automation. Whenever event happens in Browserless, workflow will start[7] from Get a Batch Scrape node.
Search for Cancel a Batch Scrape, connect it as the next step of integration sequence. You can use filters between Get a Batch Scrape and Cancel a Batch Scrape, so only important data pass from Get a Batch Scrape to the next step. WEXTL gives you full control over the process of Browserless automation. All parts of workflow are visible on the canvas[4].
Browserless on WEXTL has 39 modules for creating developer tools automations. Explore Browserless documentation for more.
- BrowserlessGet a Batch Scrape
- LaunchDarklyPerforms action
OR
- LaunchDarklyTriggers
- BrowserlessCancel a Batch Scrape
Frequently asked questions
Common questions about automating Browserless in your workflows.
What triggers does Browserless support?
Browserless has no triggers, but it provides 39 actions including "Get a Batch Scrape", "Get a Crawl", and "Get a Profile". Pair them with triggers from other apps to automate Browserless tasks.
What actions can I run in Browserless?
Integration has 39 actions, including "Get a Batch Scrape", "Get a Crawl", and "Get a Profile", and more. Refer to our Browserless Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 38 Browserless modules, like "Get a Batch Scrape", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Browserless credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Browserless?
Through the official Browserless API: 38 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Browserless?
Browserless has no triggers here. Point Browserless at a Custom Webhook node URL, or run the workflow on a schedule.
Why use WEXTL platform for Browserless automation?
WEXTL is an AI-first visual canvas: describe the Browserless flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Browserless integration.
- Browserless integration source code, module specs and credentials implementation.
- Internal Browserless integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Browserless vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Browserless App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Browserless app documentation
Explore how WEXTL® crafted Browserless integration page documentation. Used sources, the role of AI, and how the team validates the result.




















