# Connect eSignatures to Browserbase When **Contract Signed** fires in [eSignatures](https://apiant.ai/connections/esignatures), 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. eSignatures **4** triggers eSignatures **11** 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 eSignatures 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 eSignatures can start in Browserbase - When **Contract Signed** in eSignatures then **Fetch page** in Browserbase - When **Contract Withdrawn** in eSignatures 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 eSignatures and Browserbase ## Triggers and actions 4 triggers · 23 actions - Trigger **Contract Signed** Triggers when a contract is signed by all signers. - Trigger **Contract Withdrawn** Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn". - Trigger **Signer Declined Signature** Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature". - Trigger **Signer Viewed Contract** Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract". - Action **Add Signer** Add a new signer to an existing contract. - Action **Add Template** Create a new reusable contract template. - Action **Create Contract** Creates a new contract. - Action **Delete Signer** Remove a signer from a contract that has not yet signed. - Action **Delete Template** Delete a contract template. - Action **Get Contract** Retrieve a contract's current status, signer states, and metadata. - Action **Get Template** Retrieve a contract template's details. - Action **List Templates** List all contract templates in the account. - Action **Send Contract Draft** Send a previously created draft contract to its signers. - Action **Update Template** Update an existing contract template's title or settings. - Action **Withdraw Contract** Withdraw (cancel) a contract that has been sent but not fully signed. - 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 - [ **eSignatures** ESignatures.io is a tool used for signing mobile friendly contracts over the web.](https://apiant.ai/connections/esignatures) - [ **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 eSignatures - [ **eSignatures to Pexafy** Semantic image search across 9+ free stock photo sources with a unified JSON schema](https://apiant.ai/connect/esignatures-to-pexafy) - [ **eSignatures to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/esignatures-to-hubspot) - [ **eSignatures to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/esignatures-to-salesforce) - [ **eSignatures to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/esignatures-to-slack) - [ **eSignatures to Google Sheets** Google Sheets](https://apiant.ai/connect/esignatures-to-google-sheets) - [ **eSignatures to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/esignatures-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](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 ## eSignatures and Browserbase, answered ### ### What can start an automation from eSignatures? Any of eSignatures's 4 triggers in the catalog, including Contract Signed, Contract Withdrawn, Signer Declined Signature and Signer Viewed Contract. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Browserbase when something happens in eSignatures? 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 eSignatures? Browserbase has no triggers in the catalog today, so automations start in eSignatures. 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 eSignatures 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.