--- title: "Connect Chaport and Trengo - APIANT.ai" description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Add internal note to ticket\" in Trengo." canonical: "https://apiant.ai/connect/chaport-to-trengo" --- # Connect Chaport and Trengo When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Add internal note to ticket** in [Trengo](https://apiant.ai/connections/trengo), or **New Internal Note** in Trengo 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 Trengo **3** triggers Trengo **15** 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 Trengo 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 Trengo can do together ### From Chaport to Trengo - When **Chat Stage Updated (instant)** in Chaport then **Add internal note to ticket** in Trengo - When **New Chat Started** in Chaport then **Add ticket** in Trengo ### From Trengo to Chaport - When **New Internal Note** in Trengo then **Send a Message** in Chaport - When **New Outbound Message** in Trengo 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 Trengo ## Triggers and actions 11 triggers · 27 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 Internal Note** Fires when an internal note is added to a Trengo ticket. - Trigger **New Outbound Message** Triggers when an outbound message is created. - Trigger **Ticket Label Added** Triggers when a label is added to a conversation. - Action **Add internal note to ticket** Adds an internal note (visible only to agents) to a Trengo ticket. - Action **Add ticket** Create a new support ticket. - Action **Add ticket label** Attaches an existing label to a Trengo ticket. - Action **Create a Contact** Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate. - Action **Create webhook** Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation. - Action **Delete contact** Delete a contact by id. - Action **Delete ticket** Delete a ticket by id. - Action **Find a Contact** Returns the Trengo contacts that match the search term. - Action **Get contact** Retrieve a single Trengo contact by its id. - Action **Get webhook** Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found. - Action **List contacts** List all contacts. - Action **List labels** Lists the ticket labels defined in the Trengo account (first page). - Action **List tickets** Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time. - Action **Send a Message** Sends a reply message on an existing Trengo ticket, over the ticket's own channel. - Action **Update contact** Update an existing contact by id. ## Each app on its own - [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport) - [ **Trengo** Trengo is a team collaboration tool to manage conversations from channels such as web chat, email and...](https://apiant.ai/connections/trengo) 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 Trengo - [ **OpenAI to Trengo** OpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...](https://apiant.ai/connect/openai-to-trengo) - [ **CloudConvert to Trengo** CloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...](https://apiant.ai/connect/cloudconvert-to-trengo) - [ **elmah.io to Trengo** Cloud logging for.NET web applications using ELMAH.](https://apiant.ai/connect/elmah-io-to-trengo) - [ **Postman to Trengo** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-trengo) - [ **HubSpot to Trengo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-trengo) - [ **Salesforce to Trengo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-trengo) Questions ## Chaport and Trengo, 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 Trengo when something happens in Chaport? Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Trengo to Chaport? Yes. When something happens in Trengo, your agent can act in Chaport too. This page covers both directions: Trengo's triggers and Chaport's actions are listed here as well. ### ### Do I have to build a connector for Chaport or Trengo? 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 Trengo 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.