# Connect Parseur to Browserbase

When **New Document Export Failed** fires in [Parseur](https://apiant.ai/connections/parseur), your agent runs **Fetch page** in [Browserbase](https://apiant.ai/connections/browserbase). Describe the whole flow and it is built, tested on every scenario and kept running.

Parseur **6** triggers Parseur **10** actions Browserbase **12** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Parseur and Browserbase to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Parseur can start in Browserbase

- When **New Document Export Failed** in Parseur then **Fetch page** in Browserbase
- When **New Document Not Processed** in Parseur then **Add context** in Browserbase

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Parseur and Browserbase

## Triggers and actions 6 triggers · 22 actions

- Trigger

**New Document Export Failed**

Triggered when Parseur fails to export a document to its destination.

- Trigger

**New Document Not Processed**

Triggered when Parseur receives a document it cannot extract data from, so you can follow it up.

- Trigger

**New Document Processed**

Triggered when Parseur finishes extracting data from a document, with the extracted fields.

- Trigger

**New Document Processed (With List Items)**

Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).

- Trigger

**New Mailbox**

Triggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.

- Trigger

**New Table Field Processed**

Triggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.

- Action

**Create Document**

Sends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.

- Action

**Create Document From File**

Uploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.

- Action

**Delete Document**

Deletes a document from Parseur by its ID.

- Action

**Delete Mailbox**

Deletes a Parseur mailbox and everything in it. This cannot be undone.

- Action

**Get Document**

Returns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.

- Action

**Get Mailbox**

Returns one Parseur mailbox by its ID, with its email address, document counts and settings.

- Action

**List Documents**

Returns the documents in Parseur, optionally narrowed to one mailbox or one processing status.

- Action

**List Mailboxes**

Returns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.

- Action

**Reprocess Document**

Sends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.

- Action

**Update Mailbox**

Updates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.

- Action

**Add context**

Creates a new browser Context that persists cookies and storage across Browserbase sessions.

- Action

**Add session**

Creates a new Browserbase browser session and returns its id along with the URLs used to connect to it.

- Action

**Delete context**

Deletes a browser context (saved cookies and browser state) from your Browserbase project.

- Action

**Fetch page**

Fetches a web page through Browserbase and returns its content (raw, markdown, or schema-extracted JSON), status code and headers.

- Action

**Get context**

Returns a Browserbase context (saved browser state) by its id, including its name, project and timestamps.

- Action

**Get run**

Returns the current status and details of an agent run, including its result and the browser session it used.

- Action

**Get session**

Returns a Browserbase browser session, including its status, region, timestamps and connection URLs.

- Action

**List downloads**

Returns the files downloaded during a Browserbase session, optionally filtered by filename, MIME type, size or creation time.

- Action

**List sessions**

Returns the browser sessions in your Browserbase project, optionally filtered by status or by user metadata.

- Action

**Run agent**

Starts a Browserbase browser agent run that completes a natural-language task using web search and browser tools. Returns the new run, which starts in a pending state.

- Action

**Search web**

Runs a web search through Browserbase and returns the matching pages with their titles and URLs.

- Action

**Update session**

Updates a Browserbase session, such as requesting that it be released before its timeout to stop further charges.

## Each app on its own

- [ **Parseur** Send documents such as emails, PDFs and spreadsheets to your custom Parseur mailbox and extract any data.](https://apiant.ai/connections/parseur)
- [ **Browserbase** Cloud browser infrastructure API for running headless browsers to power AI agent web automation and scraping.](https://apiant.ai/connections/browserbase)

Reviews

## What our customers say

## More from Parseur

- [ **Parseur to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/parseur-to-salesforce)
- [ **Parseur to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/parseur-to-slack)
- [ **Parseur to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/parseur-to-stripe)
- [ **Parseur to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/parseur-to-shopify)
- [ **Parseur to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/parseur-to-quickbooks-online)
- [ **Parseur to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/parseur-to-pipedrive)

## More into Browserbase

- [ **HubSpot to Browserbase** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-browserbase)
- [ **Salesforce to Browserbase** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-browserbase)
- [ **Slack to Browserbase** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-browserbase)
- [ **Google Sheets to Browserbase** Google Sheets](https://apiant.ai/connect/google-sheets-to-browserbase)
- [ **Gmail to Browserbase** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-browserbase)
- [ **Google Calendar to Browserbase** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-browserbase)

Questions

## Parseur and Browserbase, answered

###

### What can start an automation from Parseur?

Any of Parseur's 6 triggers in the catalog, including New Document Export Failed, New Document Not Processed, New Document Processed and New Document Processed (With List Items). Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Browserbase when something happens in Parseur?

Any of Browserbase's 12 actions, including Update session, Add context, Add session and Fetch page. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Browserbase to Parseur?

Browserbase has no triggers in the catalog today, so automations start in Parseur. If you need the other direction, ask: your agent reads Browserbase's API documentation and adds it.

###

### Do I have to build a connector for Parseur or Browserbase?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
