# Connect Wachete to Browserbase

When **New notification for monitor** fires in [Wachete](https://apiant.ai/connections/wachete), 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.

Wachete **2** triggers Wachete **7** 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 Wachete 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 Wachete can start in Browserbase

- When **New notification for monitor** in Wachete then **Fetch page** in Browserbase
- When **Any new notification** in Wachete 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 Wachete and Browserbase

## Triggers and actions 2 triggers · 19 actions

- Trigger

**Any new notification**

Fires when there is a new change notification from any monitor in your Wachete account.

- Trigger

**New notification for monitor**

Fires when there is a new change notification from the specified Wachete monitor (taskId).

- Action

**Create monitor**

Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

- Action

**Delete monitor**

Delete a Wachete monitor by its ID.

- Action

**Get monitor**

Get information about a specific Wachete monitor by its ID.

- Action

**Get monitor data**

Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

- Action

**List folders**

List folder contents, optionally under a parent folder.

- Action

**List notifications**

List change notifications, optionally filtered by monitor (taskId) and date range.

- Action

**Update monitor**

Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

- 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

- [ **Wachete** Wachete monitors web pages (or parts of pages) for changes and notifies you when the text changes or...](https://apiant.ai/connections/wachete)
- [ **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 Wachete

- [ **Wachete to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/wachete-to-salesforce)
- [ **Wachete to ActiveCampaign** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/wachete-to-activecampaign)
- [ **Wachete to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/wachete-to-jira)
- [ **Wachete to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/wachete-to-zoom)
- [ **Wachete to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/wachete-to-webflow)
- [ **Wachete to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/wachete-to-anthropic)

## 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

## Wachete and Browserbase, answered

###

### What can start an automation from Wachete?

Any of Wachete's 2 triggers in the catalog, including New notification for monitor and Any new notification. Describe the moment in plain language and your agent picks the right one.

###

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

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 Wachete?

Browserbase has no triggers in the catalog today, so automations start in Wachete. 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 Wachete 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.
