Integration
Connect Courier to Okta
When New Audience Member fires in Courier, 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 Courier 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 Courier can start in Okta
When New Audience Member in Courier
then Add User to Group in Okta
When New Message in Courier
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 Courier and Okta
Triggers and actions 2 triggers · 40 actions
Trigger
New Audience MemberTriggers when a new user becomes a member of a Courier audience.
Trigger
New MessageTriggers when Courier sends a new message, optionally limited to one template, recipient or status.
Action
Add brandCreates a brand in Courier with a name and styling settings such as colors, logo and email header/footer.
Action
Add listCreates a list, or replaces an existing one, with the given id, name and default preferences.
Action
Create or Merge ProfileCreates a Courier user profile, or merges the given email and phone number into an existing one.
Action
Delete listDeletes a Courier list, stopping sends that target it. A deleted list can later be restored.
Action
Delete profileDeletes a user's profile and stored contact details in Courier. List subscriptions and preferences are not removed.
Action
Get audienceReturns one audience with its name, description, and the filter rules that decide which users belong to it.
Action
Get listReturns one Courier list by its id, with its name and created and updated timestamps.
Action
Get profileReturns a user's stored Courier profile, including their email address, phone number and any custom data, along with their notification preferences.
Action
Invoke journeyStarts a run of a Courier journey for one user and returns the run ID. Messages are sent asynchronously after the run starts.
Action
List audiencesReturns the audiences in your Courier workspace, each with its name, description and membership filter.
Action
List brandsReturns the brands in your Courier workspace, each with its name, styling settings, snippets and published version.
Action
List listsReturns the lists in your Courier workspace, optionally filtered by a list id pattern.
Action
List notification templatesReturns the workspace's notification templates, optionally filtered by tags or linked event.
Action
List tenantsReturns the workspace's tenants, each with its name, parent tenant, brand, properties and default preferences.
Action
Send MessageSends a notification through Courier to one recipient (a user ID, an email address, a list or an audience), using a saved template or a title and body. Returns the request ID.
Action
Subscribe User to ListSubscribes a Courier user profile to a list, creating the list if it does not exist.
Action
Unsubscribe user from listRemoves a user's subscription to a Courier list. The user's profile and other list subscriptions are left untouched.
Action
Update profileApplies a list of changes to a Courier user profile, adding, replacing or removing individual profile fields without sending the whole profile.
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 Courier
Courier to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Courier to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Courier to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Courier to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Courier to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Courier to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Courier and Okta, answered
What can start an automation from Courier?
Any of Courier's 2 triggers in the catalog, including New Audience Member and New Message. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Okta when something happens in Courier?
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 Courier?
Okta has no triggers in the catalog today, so automations start in Courier. 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 Courier 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 Courier 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.