---
title: "Connect Chaport to Dixa - APIANT.ai"
description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Set Custom Contact Attributes\" in Dixa."
canonical: "https://apiant.ai/connect/chaport-to-dixa"
---

# Connect Chaport to Dixa

When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Set Custom Contact Attributes** in [Dixa](https://apiant.ai/connections/dixa). Describe the whole flow and it is built, tested on every scenario and kept running.

Chaport **8** triggers Chaport **12** actions Dixa **23** 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 Dixa 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 can start in Dixa

- When **Chat Stage Updated (instant)** in Chaport then **Set Custom Contact Attributes** in Dixa
- When **New Chat Started** in Chaport then **Add Internal Note** in Dixa

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 Dixa

## Triggers and actions 8 triggers · 35 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.

- Action

**Add Internal Note**

Adds an internal note, visible only to agents, to a Dixa conversation and returns the created note.

- Action

**Change Conversation Status**

Changes a conversation's status by closing it, reopening it, or putting it into follow-up until a chosen time.

- Action

**Create Callback Request**

Creates a callback request conversation in Dixa, placing a call-back for an end user into the chosen queue, and returns the new conversation's id.

- Action

**Create Conversation**

Creates a new Dixa conversation on the email, contact form, chat, SMS, WhatsApp or callback channel and returns its ID.

- Action

**Create User**

Creates an end user (contact) in Dixa with their name, contact details and any custom contact attributes, and returns the new end user.

- Action

**Get Anonymization Status**

Returns the status of an anonymization request submitted earlier for a user, conversation or message, including when it was initiated and when it was processed.

- Action

**Get Conversation by Id**

Returns a single Dixa conversation by its id, including its channel, state, assignment, queue and custom attributes.

- Action

**Get Conversation Rating**

Returns the latest rating statuses and scores for a conversation, with one entry for each question of the survey.

- Action

**Get Conversation Tags**

Returns the tags applied to a conversation, including each tag's name, color and state.

- Action

**Get Messages in Conversation**

Returns all messages in a Dixa conversation, sorted from oldest to newest.

- Action

**Get Queue by Id**

Returns a Dixa queue by its id, including its name, offering settings, thresholds and the channels that use it. An error occurs if the queue is not found.

- Action

**Get User by Id**

Returns one Dixa end user (contact) by id, including their name, email addresses, phone numbers, external id and custom attribute values.

- Action

**Remove Tag From Conversation**

Removes a tag from a Dixa conversation. Active and inactive tags can both be removed.

- Action

**Search Conversation**

Returns the conversations that contain the specified text, match the specified filters, or both, with snippets showing where the text was found.

- Action

**Search Conversations by User**

Returns the conversations requested by a specific end user.

- Action

**Search Enduser by External ID**

Returns the end users whose external ID matches the value you provide.

- Action

**Search User by Email Address**

Returns the Dixa end users whose email address matches the one you provide.

- Action

**Search User by Phone Number**

Returns the Dixa end users whose phone number matches the one you specify.

- Action

**Set Custom Contact Attributes**

Sets custom attribute values on an end user in Dixa and returns the attributes that were updated.

- Action

**Set Custom Conversation Attributes**

Sets the values of custom attributes on a conversation and returns the conversation's updated custom attributes.

- Action

**Tag Conversation**

Adds an existing active tag to a conversation.

- Action

**Transfer Conversation to Queue**

Transfers a conversation to the queue you choose, optionally on behalf of a specific agent, admin or AI agent.

- Action

**Update End User**

Updates an end user's name, contact details, avatar, external ID and custom contact attributes in Dixa. Only the fields you fill in are changed.

## Each app on its own

- [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport)
- [ **Dixa** Dixa is omnichannel customer service software that unifies voice, email, chat, and messaging apps into one...](https://apiant.ai/connections/dixa)

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 Dixa

- [ **HubSpot to Dixa** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-dixa)
- [ **Salesforce to Dixa** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-dixa)
- [ **Slack to Dixa** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-dixa)
- [ **Google Sheets to Dixa** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-dixa)
- [ **Gmail to Dixa** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-dixa)
- [ **Google Calendar to Dixa** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-dixa)

Questions

## Chaport and Dixa, 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 Dixa when something happens in Chaport?

Any of Dixa's 23 actions, including Create Callback Request, Create Conversation, Create User and Update End User. Your agent maps the data both ways and tests every scenario before it ships.

###

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

Dixa has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads Dixa's API documentation and adds it.

###

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

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 Dixa 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.
