--- title: "Connect Concord CLM to Browserbase - APIANT.ai" description: "When \"New agreement\" fires in Concord CLM, your agent runs \"Fetch page\" in Browserbase." canonical: "https://apiant.ai/connect/concord-clm-to-browserbase" --- # Connect Concord CLM to Browserbase When **New agreement** fires in [Concord CLM](https://apiant.ai/connections/concord-clm), 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. Concord CLM **1** trigger Concord CLM **18** 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 Concord CLM and Browserbase to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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 Concord CLM can start in Browserbase - When **New agreement** in Concord CLM then **Fetch page** in Browserbase - When **New agreement** in Concord CLM 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 Concord CLM and Browserbase ## Triggers and actions 1 trigger · 30 actions - Trigger **New agreement** Triggers when a new agreement appears in the selected Concord organization. - Action **Add agreement** Creates a new agreement in a Concord organization, either as a blank draft, template or contract, or from an existing template or contract. Returns the new agreement's identifiers. - Action **Add attachment** Uploads a file and attaches it to a Concord agreement, and returns the ID of the new attachment. - Action **Add folder** Creates a new folder inside an existing folder of a Concord organization and returns the new folder. - Action **Add member to agreement** Invites a person to an agreement by email with the chosen permission level and sends them an invitation message. Returns the agreement's id, unique identifier and status. - Action **Create a New Document From a Template** Creates a new Concord document from an automated template, filling in its variables and optionally inviting people to it. - Action **Create an Executed Document** Creates an agreement in Concord with the status of an executed contract, rather than a draft or template. Returns the new agreement's identifiers. - Action **Create webhook - Document Fully Approved** Creates a Concord webhook integration that calls the given URL when an agreement is fully approved. - Action **Create webhook - Document Fully Signed** Creates a Concord webhook integration that calls the given address when an agreement is fully signed. - Action **Create webhook - Signature Provided** Creates a Concord webhook integration that calls the given address whenever a new signature is added to an agreement. - Action **Delete agreement** Permanently deletes an agreement from a Concord organization. - Action **Get agreement** Returns one Concord agreement by its UID, including its title, status, folder, tags, permission and creation details. An error occurs if the agreement is not found. - Action **List agreements** Returns the agreements in a Concord organization's inbox, filtered by stage and optionally by creator, tags, dates, parties and search text. - Action **List automated templates** Returns the automated templates available in a Concord organization, with each template's id, title and description. - Action **List folders** Returns the folder tree of a Concord organization: the root folder with its nested subfolders, access settings and document counts. - Action **List organizations** Returns every Concord organization the connected user belongs to, including each organization's name, subscription, and the user's role in it. - Action **Move agreement** Moves an agreement into a different folder in a Concord organization. - Action **Request signature** Requests signatures on an agreement from its signers. Colleagues are added to the agreement, external signers are emailed an invitation, and when a signing order is enabled the request goes to the next signer in that order. - Action **Update agreement** Updates the status of an existing Concord agreement, setting it to Signing or Broken. - 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 - [ **Concord CLM** Concord is a full contract lifecycle management platform with drafting, approvals, e-signature and storage -...](https://apiant.ai/connections/concord-clm) - [ **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 Concord CLM - [ **Concord CLM to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/concord-clm-to-hubspot) - [ **Concord CLM to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/concord-clm-to-salesforce) - [ **Concord CLM to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/concord-clm-to-slack) - [ **Concord CLM to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/concord-clm-to-google-sheets) - [ **Concord CLM to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/concord-clm-to-gmail) - [ **Concord CLM to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/concord-clm-to-google-calendar) ## 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 ## Concord CLM and Browserbase, answered ### ### What can start an automation from Concord CLM? Any of Concord CLM's 1 trigger in the catalog, including New agreement. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Browserbase when something happens in Concord CLM? 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 Concord CLM? Browserbase has no triggers in the catalog today, so automations start in Concord CLM. 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 Concord CLM 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. ### ### Can my AI client use Concord CLM and Browserbase without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### 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.