Integration
Connect Openmic to Okta
When New Post-Call Summary fires in Openmic, your agent runs Add User to Group in Okta. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Openmic and Okta to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What Openmic can start in Okta
When New Post-Call Summary in Openmic
then Add User to Group in Okta
When New Post-Call Summary in Openmic
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 Openmic and Okta
Triggers and actions 1 trigger · 59 actions
Trigger
New Post-Call SummaryTriggers when an Openmic call finishes, returning the completed call's numbers, agent, status and details.
Action
Add a ContactAdds a single contact to the list.
Action
Bulk Add ContactsAdds up to 1 000 contacts to the list in a single request.
Action
Create a CampaignCreates a new outbound dialing campaign. The campaign will begin dialing contacts within the `time_start`–`time_end` window on the specified `days`. If `timezone` is omitted the organization's default timezone is used.
Action
Create a Contact ListCreate a contact list
Action
Create an AgentCreates a new voice AI agent. > **Note:** `first_message` and `auto_first_message` are mutually exclusive. Providing both returns a `400` error.
Action
Create a Phone CallInitiates a new outbound phone call from a number registered in your organization. **Rate limit:** 5 requests per minute.
Action
Create a Tool for an AgentAdds a new tool to the agent's toolset. When `type` is `api_request`, the `url` field is **required**.
Action
Delete a CampaignDelete a campaign
Action
Delete a Contact ListDelete a contact list
Action
Delete an AgentPermanently deletes an agent. Returns `409 Conflict` if the agent is currently linked to a phone number or campaign.
Action
Delete a ToolPermanently removes a tool from the agent.
Action
Delete Contacts from a ListBulk-deletes contacts by their IDs. Accepts up to 1 000 IDs per request.
Action
Find BotReturns the full details of a single agent.
Action
Find CallReturns details and current status of a single call by its CUID.
Action
Get a CampaignGet a campaign
Action
Get a Contact ListGet a contact list
Action
Get an SMS LogReturns a single SMS log entry enriched with message details fetched live from the SMS provider: message body, delivery status, sent/delivered timestamps, and failure reason. If provider details are unavailable, the entry is returned with `status: "u
Action
Get a Phone NumberReturns details for a single phone number including linked agents.
Action
Get a ToolReturns details for a single tool.
Action
Get a VoiceReturns details for a single voice by its numeric ID.
Action
Get CallsReturns a cursor-paginated list of calls, newest first.
Action
Get UsageReturns call-minutes and sent-SMS usage for your organization, grouped by day, week, or month (UTC buckets; weekly buckets start on Monday). When from_date is omitted, the range defaults to the last 30 days for day, 12 weeks for week, and 12 months f
Action
Link an Agent to a Phone NumberAssociates an agent with a phone number for the given `direction`. | Direction | Effect | |-----------|--------| | `inbound` | Agent handles incoming calls on this number | | `outbound` | Agent is used as the default for outbound calls from this num
Action
List CampaignsReturns a cursor-paginated list of campaigns, newest first.
Action
List Contact ListsList contact lists
Action
List Contacts in a ListList contacts in a list
Action
List Phone NumbersReturns a cursor-paginated list of phone numbers in your organization.
Action
List SMS LogsReturns a cursor-paginated list of SMS log entries for your organization, newest first. Entries contain delivery metadata (direction, phone numbers, timestamps) — message bodies are not stored.
Action
List Tools for an AgentReturns a cursor-paginated list of tools attached to the agent.
Action
List VoicesReturns a cursor-paginated catalogue of available voices. Use the `voice` field from a voice record when creating or updating an agent.
Action
Send SMSSend an SMS message to a phone number. Messages are queued for delivery.
Action
Unlink an Agent from a Phone NumberRemoves the agent association from a phone number for the given direction.
Action
Update a CampaignPartially updates a campaign. Only the fields you include are modified.
Action
Update a ContactPartially updates a single contact.
Action
Update a Contact ListUpdate a contact list
Action
Update an AgentPartially updates an agent. Only the fields you include are modified. Set `knowledge_base_id` to `null` to detach the current knowledge base.
Action
Update a ToolPartially updates a tool. Only the fields you include are modified.
Action
Activate UserActivates a staged or deprovisioned Okta user and returns their activation link and token. Activation emails the user unless turned off.
Action
Add groupCreates 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 GroupAdds an existing Okta user to an Okta-managed group.
Action
Assign user to applicationAssigns an existing Okta user to an application, optionally setting their app username, password and app profile. Returns the resulting application user.
Action
Create UserCreates a new user in your Okta org, with or without credentials, and returns the new user's id and status.
Action
Deactivate UserDeactivates 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 groupPermanently deletes a group from your Okta org by its ID.
Action
Delete userPermanently 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 NameReturns the Okta groups whose name matches the name you specify, either exactly or by a partial match.
Action
Find User by EmailReturns the Okta users whose primary email matches the email you specify, including deprovisioned users.
Action
Get groupReturns one Okta group by its id, including its profile name, description and any custom attributes.
Action
Get userReturns 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 applicationsReturns the applications in your Okta org, optionally narrowed by a name or label prefix or a filter expression.
Action
List group membersReturns 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 groupsReturns the groups in your Okta organization, optionally narrowed by a search, filter or name match.
Action
List usersReturns the users in your Okta organization, optionally narrowed by a search, filter or name query.
Action
Remove User From GroupRemoves a user from a group managed directly in Okta. The user account itself is not changed.
Action
Reset user passwordStarts 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 UserSuspends 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 userUnsuspends a suspended Okta user and returns them to the Active state.
Action
Update groupUpdates the name, description or custom attributes of an Okta-managed group. Anything left blank keeps its current value.
Action
Update userUpdates an existing Okta user's profile, including custom profile attributes, or credentials. Fields left blank keep their current values.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Openmic
Openmic to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Openmic to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Openmic to StripeStripe is a payment processing platform for online businesses.
Openmic to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Openmic to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Openmic to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Okta
HubSpot to OktaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to OktaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to OktaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to OktaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OktaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OktaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Openmic and Okta, answered
What can start an automation from Openmic?
Any of Openmic's 1 trigger in the catalog, including New Post-Call Summary. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Okta when something happens in Openmic?
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 Openmic?
Okta has no triggers in the catalog today, so automations start in Openmic. 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 Openmic 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 Openmic 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.