--- title: "Connect Chaport and inMobile - SMS gateway - APIANT.ai" description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Create or Update Contact\" in inMobile - SMS gateway." canonical: "https://apiant.ai/connect/chaport-to-inmobile-sms-gateway" --- # Connect Chaport and inMobile - SMS gateway When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Create or Update Contact** in [inMobile - SMS gateway](https://apiant.ai/connections/inmobile-sms-gateway), or **New email event** in inMobile - SMS gateway 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 inMobile - SMS gateway **4** triggers inMobile - SMS gateway **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 inMobile - SMS gateway 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 inMobile - SMS gateway can do together ### From Chaport to inMobile - SMS gateway - When **Chat Stage Updated (instant)** in Chaport then **Create or Update Contact** in inMobile - SMS gateway - When **New Chat Started** in Chaport then **Send email** in inMobile - SMS gateway ### From inMobile - SMS gateway to Chaport - When **New email event** in inMobile - SMS gateway then **Send a Message** in Chaport - When **New incoming RCS message** in inMobile - SMS gateway 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 inMobile - SMS gateway ## Triggers and actions 12 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 email event** Triggers when a new email event occurs on a message you sent, such as delivered, opened, clicked, bounced or unsubscribed. - Trigger **New incoming RCS message** Triggers when a new RCS message is received by one of your inMobile RCS agents, including text, file, location and suggestion responses. - Trigger **New incoming SMS message** Triggers when a new SMS message is received on one of your inMobile numbers. - Trigger **New SMS status report** Triggers when a delivery status report arrives for a sent SMS message. inMobile hands out each report only once, so a report collected by this trigger can't be retrieved again through the API. - Action **Add list** Creates a new recipient list in your inMobile account and returns its id, name and creation time. - Action **Add Mobile Number to Blacklist** Adds a mobile number to the inMobile blacklist so it no longer receives messages, and returns the created blacklist entry. - Action **Add recipient** Creates a recipient with a phone number and optional contact details on an inMobile SMS list, and returns the new recipient. - Action **Cancel SMS message** Cancels scheduled SMS messages that have not been sent yet and returns a result for each message. - Action **Create or Update Contact** Creates a recipient on an inMobile list, or updates the existing recipient on that list with the same phone number. - Action **Delete Contact** Deletes a contact (recipient) from an inMobile list. - Action **Find recipient by number** Returns the recipient on an inMobile list that has the specified phone number, and reports whether one was found. - Action **List lists** Returns all recipient lists in the inMobile account, with each list's id, name and creation time. - Action **List recipients** Returns all recipients in an inMobile list, including their phone numbers and fields. - Action **Parse phone numbers** Checks a list of phone numbers and returns, for each one, whether it is valid along with its cleaned number, country code and local number. - Action **Remove Mobile Number From Blacklist** Removes a mobile number from your inMobile blacklist, so it can receive messages again. - Action **Send email** Sends an email with a subject and HTML body to up to 100 recipients through inMobile, optionally scheduled for later, and returns the message id and accepted recipients. - Action **Send RCS text message** Sends a text-only RCS message from one of your RCS agents to a mobile number, with optional suggested replies and actions. Returns the message id and the parsed recipient number. - Action **Send SMS Message** Sends one SMS text message to a mobile number, immediately or at a scheduled time, and returns the message ID and how many SMS parts it uses. - Action **Update recipient** Updates an existing recipient on an inMobile list. Only the details you fill in are changed; anything left blank keeps its current value. ## Each app on its own - [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport) - [ **inMobile - SMS gateway** inMobile is a powerful SMS gateway. inMobile makes it easy for you to send personalized SMS messages, manage...](https://apiant.ai/connections/inmobile-sms-gateway) 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 inMobile - SMS gateway - [ **HubSpot to inMobile - SMS gateway** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-inmobile-sms-gateway) - [ **Google Sheets to inMobile - SMS gateway** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-inmobile-sms-gateway) - [ **Gmail to inMobile - SMS gateway** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-inmobile-sms-gateway) - [ **Google Calendar to inMobile - SMS gateway** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-inmobile-sms-gateway) - [ **Google Drive to inMobile - SMS gateway** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-inmobile-sms-gateway) - [ **ActiveCampaign to inMobile - SMS gateway** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-inmobile-sms-gateway) Questions ## Chaport and inMobile - SMS gateway, 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 inMobile - SMS gateway when something happens in Chaport? Any of inMobile - SMS gateway's 15 actions, including Create or Update Contact, Send email, Send RCS text message and Send SMS Message. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from inMobile - SMS gateway to Chaport? Yes. When something happens in inMobile - SMS gateway, your agent can act in Chaport too. This page covers both directions: inMobile - SMS gateway's triggers and Chaport's actions are listed here as well. ### ### Do I have to build a connector for Chaport or inMobile - SMS gateway? 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 inMobile - SMS gateway 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.