Developer Tools · Integration
Browserless
Add Browserless to your product for your customers, and give your AI agents governed access to it.
Browserless is hosted headless Chrome reached two ways: a WebSocket endpoint that Puppeteer or Playwright connect to with connect() and a token query parameter, or REST endpoints such as /content, /screenshot, /pdf, /scrape and /function for one-shot jobs that need no local browser library. Requests go to a regional host chosen when the account is created, so a token issued for one region will not authenticate against another. Each plan sets a concurrency limit and a per-session timeout, and exceeding concurrency queues or rejects connections rather than slowing them, so retry logic matters more than it does with a plain HTTP API. Long-lived sessions are killed at the timeout even mid-navigation, which is the usual cause of half-written screenshots. The category nouns of services, builds and deployments are the least-wrong fit; the real objects are browser sessions and job responses. fastn holds each customer's token and region, keeps the connection healthy and limits what an agent may run.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Browserless account so browser jobs run on their concurrency and their token.
Render a PDF or screenshot of a customer-supplied URL and attach the file to a record.
Extract page content from sites with no API using the scrape endpoint and store the parsed fields.
Run a customer's own Puppeteer script against the hosted browser without shipping Chrome in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent fetch rendered page content for an allow-listed domain, with session count and duration audited per tenant.
Have an agent capture a screenshot of a page and report what it sees when a customer files a rendering complaint.
Allow an agent to use the read-only content and screenshot endpoints while blocking arbitrary function execution.
Example prompt
Take a full-page screenshot of this URL and tell me if the pricing table renders.
Set up Browserless in 4 steps
- 01Enable the Browserless connector from your fastn dashboard.
- 02Have each customer authorise their own Browserless account, so calls run under their credentials rather than a shared key.
- 03Decide which services, builds and deployments your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Browserless integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Browserless integration without building it. Your customers connect their own Browserless account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Browserless update is not your on-call problem.
- One integration serves your product and your agents. The same governed Browserless connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHub
Azure DevOps
Google CloudOften used alongside
Tools the same teams tend to run next to Browserless, across other categories.
Slack
Snowflake
Airtable
PostgreSQLBrowserless integration FAQ
How do I add a Browserless integration to my product?
Enable the Browserless connector in your fastn dashboard, then let each customer authenticate their own Browserless account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Browserless client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Browserless account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Browserless account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Browserless integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent fetch rendered page content for an allow-listed domain, with session count and duration audited per tenant.
Who maintains the Browserless integration?
fastn does. When Browserless changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Browserless events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Browserless?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Browserless integration?
A common starting point: let a customer connect their own Browserless account so browser jobs run on their concurrency and their token. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Browserless integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Browserless does not change your per-connector cost. You can start free with 3 connected accounts.
Add Browserless to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.