--- title: "Connect inMobile - SMS gateway and Sorry - APIANT.ai" description: "When \"New email event\" fires in inMobile - SMS gateway, your agent runs \"Update status page\" in Sorry." canonical: "https://apiant.ai/connect/inmobile-sms-gateway-to-sorry" --- # Connect inMobile - SMS gateway and Sorry When **New email event** fires in [inMobile - SMS gateway](https://apiant.ai/connections/inmobile-sms-gateway), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Create or Update Contact** in inMobile - SMS gateway. Describe the whole flow and it is built, tested on every scenario and kept running. inMobile - SMS gateway **4** triggers inMobile - SMS gateway **15** actions Sorry **1** trigger Sorry **16** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want inMobile - SMS gateway and Sorry 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 inMobile - SMS gateway and Sorry can do together ### From inMobile - SMS gateway to Sorry - When **New email event** in inMobile - SMS gateway then **Update status page** in Sorry - When **New incoming RCS message** in inMobile - SMS gateway then **Add component** in Sorry ### From Sorry to inMobile - SMS gateway - When **New notice** in Sorry then **Create or Update Contact** in inMobile - SMS gateway - When **New notice** in Sorry then **Send email** in inMobile - SMS gateway 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 inMobile - SMS gateway and Sorry ## Triggers and actions 5 triggers · 31 actions - 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. - Trigger **New notice** Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page. - Action **Add component** Creates a new component on a Sorry status page, optionally nested under a parent component. - Action **Add notice** Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers. - Action **Add notice update** Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations. - Action **Add subscriber** Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices. - Action **Delete notice** Deletes a notice (incident, maintenance or general) from a Sorry status page. - Action **Delete subscriber** Permanently removes a subscriber from a status page. - Action **Get notice** Returns a single notice from a status page, including its type, state, subject, synopsis and link. - Action **Get status page** Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more. - Action **List components** Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state. - Action **List notices** Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date. - Action **List notice updates** Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content. - Action **List status pages** Returns all status pages in your Sorry account, optionally filtered by name or creation date. - Action **List subscribers** Returns the subscribers on a status page, optionally only those who receive notices for a specific component. - Action **Update component** Updates a component on a Sorry status page, such as its name, description, position or parent component. - Action **Update notice** Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance. - Action **Update status page** Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language. ## Each app on its own - [ **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) - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) Reviews ## What our customers say ## More from inMobile - SMS gateway - [ **inMobile - SMS gateway to Mailercloud** Mailercloud is a cloud-based email marketing platform that allows businesses to launch email marketing...](https://apiant.ai/connect/inmobile-sms-gateway-to-mailercloud) - [ **inMobile - SMS gateway to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/inmobile-sms-gateway-to-salesforce) - [ **inMobile - SMS gateway to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/inmobile-sms-gateway-to-slack) - [ **inMobile - SMS gateway to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/inmobile-sms-gateway-to-mailchimp) - [ **inMobile - SMS gateway to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/inmobile-sms-gateway-to-stripe) - [ **inMobile - SMS gateway to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/inmobile-sms-gateway-to-shopify) ## More into Sorry - [ **HubSpot to Sorry** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sorry) - [ **Salesforce to Sorry** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sorry) - [ **Slack to Sorry** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sorry) - [ **Google Sheets to Sorry** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-sorry) - [ **Gmail to Sorry** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sorry) - [ **Google Calendar to Sorry** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sorry) Questions ## inMobile - SMS gateway and Sorry, answered ### ### What can start an automation from inMobile - SMS gateway? Any of inMobile - SMS gateway's 4 triggers in the catalog, including New email event, New incoming RCS message, New incoming SMS message and New SMS status report. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Sorry when something happens in inMobile - SMS gateway? Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Sorry to inMobile - SMS gateway? Yes. When something happens in Sorry, your agent can act in inMobile - SMS gateway too. This page covers both directions: Sorry's triggers and inMobile - SMS gateway's actions are listed here as well. ### ### Do I have to build a connector for inMobile - SMS gateway or Sorry? 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 inMobile - SMS gateway and Sorry 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.