Integration
Connect Knorish to Okta
When New Signup fires in Knorish, 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 Knorish 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 Knorish can start in Okta
When New Signup in Knorish
then Add User to Group in Okta
When Bundle Purchased in Knorish
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 Knorish and Okta
Triggers and actions 3 triggers · 49 actions
Trigger
Bundle PurchasedTriggers when a user is newly enrolled in the chosen bundle, such as after purchasing it.
Trigger
Course PurchasedTriggers when a user purchases or is enrolled in the selected Knorish course.
Trigger
New SignupTriggers when a new user signs up on your Knorish site.
Action
Add User to BundleGives a user access to a bundle.
Action
Add User to CourseEnrolls a user in a course.
Action
Create UserCreates a learner account on your Knorish site and returns its id.
Action
Delete BundleRemoves a bundle from your Knorish site.
Action
Delete CourseRemoves a course from your Knorish site.
Action
Delete UserRemoves a user from your Knorish site.
Action
Get BundleReturns a bundle's details by bundle id.
Action
Get CourseReturns a course's details by course id.
Action
Get UserReturns a user's profile by user id.
Action
Get User Course ProgressReturns how far a user has progressed in a course and their average assessment score.
Action
List Bundle CoursesReturns the courses included in a bundle.
Action
List BundlesReturns a page of bundles on your Knorish site.
Action
List Bundle UsersReturns the users who have a bundle, optionally filtered by date range.
Action
List Course AssessmentsReturns a course's assessments with their duration, attempts and pass marks.
Action
List Course Live SessionsReturns a course's live sessions with start/end times and host/join links.
Action
List CoursesReturns a page of courses on your Knorish site.
Action
List Course SectionsReturns a course's sections, including their drip-release settings.
Action
List Course UsersReturns the users enrolled in a course, optionally filtered by enrollment date range.
Action
List Section ChaptersReturns the chapters (lectures) in a course section.
Action
List User BundlesReturns the bundles a user has purchased or been given.
Action
List User CoursesReturns the courses a user is enrolled in, with the date each was assigned.
Action
List User Live SessionsReturns the live sessions available to a user, with start/end times and join links.
Action
List UsersReturns a page of users on your Knorish site, optionally filtered by search text or signup date range.
Action
Remove User From BundleRemoves a user's access to a bundle.
Action
Remove User From CourseRemoves a user's access to a course.
Action
Reply to ContactSends a reply to a contact form submission on your Knorish site.
Action
Update UserUpdates a user's name, email or password.
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 Knorish
Knorish to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Knorish to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Knorish to MailchimpMailchimp marketing automation and email platform.
Knorish to StripeStripe is a payment processing platform for online businesses.
Knorish to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Knorish to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
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
Knorish and Okta, answered
What can start an automation from Knorish?
Any of Knorish's 3 triggers in the catalog, including New Signup, Bundle Purchased and Course Purchased. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Okta when something happens in Knorish?
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 Knorish?
Okta has no triggers in the catalog today, so automations start in Knorish. 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 Knorish 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 Knorish 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.