--- title: "Connect inMobile - SMS gateway to Okta - APIANT.ai" description: "When \"New email event\" fires in inMobile - SMS gateway, your agent runs \"Add User to Group\" in Okta." canonical: "https://apiant.ai/connect/inmobile-sms-gateway-to-okta" --- # Connect inMobile - SMS gateway to Okta When **New email event** fires in [inMobile - SMS gateway](https://apiant.ai/connections/inmobile-sms-gateway), your agent runs **Add User to Group** in [Okta](https://apiant.ai/connections/okta). 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 Okta **22** 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 Okta 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 can start in Okta - When **New email event** in inMobile - SMS gateway then **Add User to Group** in Okta - When **New incoming RCS message** in inMobile - SMS gateway then **Create User** in Okta 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 Okta ## Triggers and actions 4 triggers · 37 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. - Action **Activate User** Activates a staged or deprovisioned Okta user and returns their activation link and token. Activation emails the user unless turned off. - Action **Add group** Creates a new Okta-managed group with a name, an optional description, and any custom group profile attributes defined in your org. - Action **Add User to Group** Adds an existing Okta user to an Okta-managed group. - Action **Assign user to application** Assigns an existing Okta user to an application, optionally setting their app username, password and app profile. Returns the resulting application user. - Action **Create User** Creates a new user in your Okta org, with or without credentials, and returns the new user's id and status. - Action **Deactivate User** Deactivates an Okta user, deprovisioning them from all assigned apps. This cannot be undone by the deactivation itself and may destroy the user's data in those apps. - Action **Delete group** Permanently deletes a group from your Okta org by its ID. - Action **Delete user** Permanently deletes a deactivated Okta user. If the user is still active, this deactivates them instead, and running it a second time deletes them. - Action **Find Group by Name** Returns the Okta groups whose name matches the name you specify, either exactly or by a partial match. - Action **Find User by Email** Returns the Okta users whose primary email matches the email you specify, including deprovisioned users. - Action **Get group** Returns one Okta group by its id, including its profile name, description and any custom attributes. - Action **Get user** Returns one Okta user, including their status, timestamps, credentials summary, and standard and custom profile attributes. An error occurs if the user is not found. - Action **List applications** Returns the applications in your Okta org, optionally narrowed by a name or label prefix or a filter expression. - Action **List group members** Returns the users who are members of an Okta group, with their profiles, including any custom attributes. Results can be narrowed with a search expression. - Action **List groups** Returns the groups in your Okta organization, optionally narrowed by a search, filter or name match. - Action **List users** Returns the users in your Okta organization, optionally narrowed by a search, filter or name query. - Action **Remove User From Group** Removes a user from a group managed directly in Okta. The user account itself is not changed. - Action **Reset user password** Starts a password reset for an Okta user and either emails them the reset link or returns the link. The user moves to Recovery status and can't sign in until they finish the reset. - Action **Suspend User** Suspends an active Okta user so they can't sign in, while keeping their group and app assignments. Suspended users can later be unsuspended or deactivated. - Action **Unsuspend user** Unsuspends a suspended Okta user and returns them to the Active state. - Action **Update group** Updates the name, description or custom attributes of an Okta-managed group. Anything left blank keeps its current value. - Action **Update user** Updates an existing Okta user's profile, including custom profile attributes, or credentials. Fields left blank keep their current values. ## 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) - [ **Okta** Okta helps companies manage and secure user authentication into modern applications, and for developers to...](https://apiant.ai/connections/okta) 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 Okta - [ **HubSpot to Okta** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-okta) - [ **Salesforce to Okta** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-okta) - [ **Slack to Okta** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-okta) - [ **Google Sheets to Okta** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-okta) - [ **Gmail to Okta** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-okta) - [ **Google Calendar to Okta** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-okta) Questions ## inMobile - SMS gateway and Okta, 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 Okta when something happens in inMobile - SMS gateway? Any of Okta's 22 actions, including Create User, Update group, Update user and Activate User. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Okta to inMobile - SMS gateway? Okta has no triggers in the catalog today, so automations start in inMobile - SMS gateway. If you need the other direction, ask: your agent reads Okta's API documentation and adds it. ### ### Do I have to build a connector for inMobile - SMS gateway or Okta? 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 Okta 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.