# Connect Docparser to Browserbase When **Parsed Document Data Available** fires in [Docparser](https://apiant.ai/connections/docparser), 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. Docparser **2** triggers Docparser **2** 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 Docparser 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 Docparser can start in Browserbase - When **Parsed Document Data Available** in Docparser then **Fetch page** in Browserbase - When **Parsed Table Row Available** in Docparser 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 Docparser and Browserbase ## Triggers and actions 2 triggers · 14 actions - Trigger **Parsed Document Data Available** Triggers whenever a new Document is processed and parsed data is available. - Trigger **Parsed Table Row Available** Triggers whenever a new Document is processed and parsed table rows are available. - Action **Fetch Document From URL** Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger). - Action **Upload Document** Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger). - 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 - [ **Docparser** Docparser converts your PDF documents into structured and easy-to-handle data.](https://apiant.ai/connections/docparser) - [ **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 Docparser - [ **Docparser to Prismix** Real-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required](https://apiant.ai/connect/docparser-to-prismix) - [ **Docparser to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/docparser-to-hubspot) - [ **Docparser to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/docparser-to-salesforce) - [ **Docparser to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/docparser-to-slack) - [ **Docparser to Google Sheets** Google Sheets](https://apiant.ai/connect/docparser-to-google-sheets) - [ **Docparser to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/docparser-to-gmail) ## 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 ## Docparser and Browserbase, answered ### ### What can start an automation from Docparser? Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Browserbase when something happens in Docparser? 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 Docparser? Browserbase has no triggers in the catalog today, so automations start in Docparser. 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 Docparser 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.