--- title: "Connect Reply to Okta - APIANT.ai" description: "When \"New Email Opened\" fires in Reply, your agent runs \"Add User to Group\" in Okta." canonical: "https://apiant.ai/connect/reply-to-okta" --- # Connect Reply to Okta When **New Email Opened** fires in [Reply](https://apiant.ai/connections/reply), 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. Reply **7** triggers Reply **16** 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 Reply 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 Reply can start in Okta - When **New Email Opened** in Reply then **Add User to Group** in Okta - When **New Emails Sent** in Reply 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 Reply and Okta ## Triggers and actions 7 triggers · 38 actions - Trigger **Inbox Category Set for Reply** Triggers when an email reply in Reply is given an inbox category, automatically or by a user. - Trigger **New Email Opened** Triggers when a contact opens a tracked email sent from Reply. - Trigger **New Emails Sent** Triggers when Reply sends an email from a sequence step. - Trigger **New Link Clicked** Triggers when a recipient clicks a tracked link in an email sent from Reply. - Trigger **New Person Bounce** Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server. - Trigger **New Person Opt Out** Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact). - Trigger **Prospect Finished** Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually. - Action **Add contact list** Creates a new contact list in Reply, optionally shared with your team. - Action **Add note to contact** Adds a note to a contact's timeline in Reply. - Action **Add sequence** Creates a new sequence in Reply with its steps, schedule, sending accounts and settings. - Action **Create\Update Person** Creates a Reply contact, or updates the existing contact with the same email address. - Action **Delete contact** Deletes a contact from your Reply account. - Action **Find contacts by criteria** Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step. - Action **Get contact** Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields. - Action **Get sequence** Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps. - Action **List contact lists** Returns the contact lists you own plus those shared with your team, optionally filtered by name. - Action **List contacts** Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL. - Action **List inbox categories** Returns the inbox categories you can file conversations under. - Action **List Sequence Contacts** Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status. - Action **List sequences** Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name. - Action **Mark as Finished** Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps. - Action **Remove Person From Campaign** Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account. - Action **Send Test Webhook Event** Sends a test event from an existing Reply webhook subscription to its configured URL. - 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 - [ **Reply** Reply is a sales automation platform that puts outreach on autopilot, while still making each communication...](https://apiant.ai/connections/reply) - [ **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 Reply - [ **Reply to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/reply-to-salesforce) - [ **Reply to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/reply-to-slack) - [ **Reply to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/reply-to-stripe) - [ **Reply to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/reply-to-shopify) - [ **Reply to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/reply-to-trello) - [ **Reply to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/reply-to-zoom) ## 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 ## Reply and Okta, answered ### ### What can start an automation from Reply? Any of Reply's 7 triggers in the catalog, including New Email Opened, New Emails Sent, New Link Clicked and New Person Bounce. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Okta when something happens in Reply? 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 Reply? Okta has no triggers in the catalog today, so automations start in Reply. 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 Reply 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 Reply 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.