---
title: "Connect Chaport and Nimbata - APIANT.ai"
description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Get lead\" in Nimbata."
canonical: "https://apiant.ai/connect/chaport-to-nimbata"
---

# Connect Chaport and Nimbata

When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Get lead** in [Nimbata](https://apiant.ai/connections/nimbata), or **New form submission** in Nimbata to **Send a Message** in Chaport. Describe the whole flow and it is built, tested on every scenario and kept running.

Chaport **8** triggers Chaport **12** actions Nimbata **1** trigger Nimbata **10** actions

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

## What do you want Chaport and Nimbata 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 Chaport and Nimbata can do together

### From Chaport to Nimbata

- When **Chat Stage Updated (instant)** in Chaport then **Get lead** in Nimbata
- When **New Chat Started** in Chaport then **List leads** in Nimbata

### From Nimbata to Chaport

- When **New form submission** in Nimbata then **Send a Message** in Chaport
- When **New form submission** in Nimbata then **Create an Operator** in Chaport

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 Chaport and Nimbata

## Triggers and actions 9 triggers · 22 actions

- Trigger

**Chat Closed (instant)**

Fires when a chat is closed. Webhook event: chat.closed.

- Trigger

**Chat Finished**

Triggers when chat is finished.

- Trigger

**Chat Stage Updated (instant)**

Fires when a chat's stage changes. Webhook event: chat.stageUpdated.

- Trigger

**Message Read (instant)**

Fires when a message is read. Webhook event: message.read.

- Trigger

**New Chat Started**

Triggers when chat is started.

- Trigger

**New Message Sent (instant)**

Fires when a new message is sent in a chat. Webhook event: message.sent.

- Trigger

**New Visitor (instant)**

Fires when a new visitor is created. Webhook event: visitor.created.

- Trigger

**Visitor Updated**

Triggers when visitor data is updated.

- Action

**Create an Operator**

Adds a new operator to your Chaport account and returns the created operator.

- Action

**Delete a Message**

Deletes one message from a Chaport chat. Identify the visitor and the message you want removed.

- Action

**Delete an Operator**

Removes an operator from your Chaport account.

- Action

**List Operators**

Returns every operator in your Chaport account, with each operator's name, email, role and status.

- Action

**List Visitors**

Returns the visitors in your Chaport account, one page at a time.

- Action

**Retrieve an Operator**

Returns one Chaport operator with their name, email, role, job title and current status.

- Action

**Retrieve a Visitor**

Returns one Chaport visitor with their name, contact details, notes and any custom data held about them.

- Action

**Retrieve Last Visitor Chat**

Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.

- Action

**Send a Message**

Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open.

- Action

**Update an Operator**

Updates a Chaport operator's details. Anything you leave blank keeps its current value.

- Action

**Update a Visitor**

Updates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.

- Action

**Update Operator Status**

Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time.

- Trigger

**New form submission**

Triggers when a new form submission is received in a Nimbata project.

- Action

**Add tag**

Creates a new tag in a tag category of a Nimbata project, ready to be applied to calls and form submissions.

- Action

**Add tags to call**

Adds one or more tags to a call and keeps the tags it already has. Returns the call's full list of tag IDs after the change.

- Action

**Get call**

Returns an inbound call's details, including its attribution, call-flow information and custom field values.

- Action

**Get lead**

Returns one lead with its phone numbers, emails, and first and last interaction details. If the lead was merged into another, returns the surviving lead.

- Action

**Get tracking number**

Returns one tracking number from a project, looked up by its ID or phone number, including its status, line type, country, call flow and tracking source.

- Action

**List calls**

Returns the inbound and outbound calls of a project, newest first, optionally narrowed by date range, caller, tracking number, outcome or campaign.

- Action

**List form submissions**

Returns the form submissions recorded in a Nimbata project, optionally narrowed by form, date range, attribution, device, tag or value.

- Action

**List leads**

Returns the identified leads in a Nimbata project, most recent interaction first, optionally narrowed to one phone number or email address.

- Action

**List SMS messages**

Returns a project's SMS messages, newest first, optionally filtered by date range, direction, status or phone number.

- Action

**List tracking numbers**

Returns the tracking numbers in a Nimbata project, optionally narrowed by a name or phone number search.

## Each app on its own

- [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport)
- [ **Nimbata** Nimbata is a call tracking platform that lets you attribute phone calls back to keyword searches, web pages...](https://apiant.ai/connections/nimbata)

Reviews

## What our customers say

## More from Chaport

- [ **Chaport to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/chaport-to-stripe)
- [ **Chaport to Chatrace** Omnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...](https://apiant.ai/connect/chaport-to-chatrace)
- [ **Chaport to keycdn IP Location Finder** Get the IP geolocation data through the simple REST API. All the responses are JSON encoded](https://apiant.ai/connect/chaport-to-keycdn-ip-location-finder)
- [ **Chaport to ProxiedMail** ProxiedMail provides creating email addresses, forwarding and receiving emails with full context.](https://apiant.ai/connect/chaport-to-proxiedmail)
- [ **Chaport to Publica** With Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...](https://apiant.ai/connect/chaport-to-publica)
- [ **Chaport to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/chaport-to-hubspot)

## More into Nimbata

- [ **HubSpot to Nimbata** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-nimbata)
- [ **Google Sheets to Nimbata** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-nimbata)
- [ **Gmail to Nimbata** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-nimbata)
- [ **Google Calendar to Nimbata** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-nimbata)
- [ **Google Drive to Nimbata** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-nimbata)
- [ **Mailchimp to Nimbata** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-nimbata)

Questions

## Chaport and Nimbata, answered

###

### What can start an automation from Chaport?

Any of Chaport's 8 triggers in the catalog, including Chat Stage Updated (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Nimbata when something happens in Chaport?

Any of Nimbata's 10 actions, including Add tag, Add tags to call, Get call and Get lead. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Nimbata to Chaport?

Yes. When something happens in Nimbata, your agent can act in Chaport too. This page covers both directions: Nimbata's triggers and Chaport's actions are listed here as well.

###

### Do I have to build a connector for Chaport or Nimbata?

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 Chaport and Nimbata 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.
