Skip to content
Okta logo

Okta integration

Developer Tools & Infrastructure · 4 actions · Custom auth

Manage users and user-type metadata in an Okta tenant via the Okta Management REST API (``/api/v1`` under your Okta subdomain).

The ModuleX Okta integration lets a ModuleX agent operate Okta on your behalf, running create, update and list actions across users and type id options, directly from a plain-English request, using your organization's own Okta credentials. No pre-built workflow is required: the agent picks the right Okta action for the task.

Okta is a developer tools & infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Okta action. Or, when you want a repeatable process, the composer assembles a Okta workflow for you, streaming the nodes onto the canvas as it builds.

Drive Okta in plain English

Type what you want. A ModuleX agent picks the right Okta action, or chains several, and runs it. No workflow to build.

  • Create a new user in the Okta tenant
    resolves tocreate_user
  • Find the user I describe and update it
    resolves toget_userupdate_user
  • Show me the type id options that match what I describe
    resolves tolist_type_id_options

What you can automate with Okta

  • Find the right user and update it in one promptget_userupdate_user
  • Pull a list of type id options for a reportlist_type_id_options
  • Create a new user in the Okta tenantcreate_user

Okta integration at a glance

VendorOkta
Actions available4
AuthenticationCustom
Uses your own credentialsYes
Works with the assistantYes
Works in the composerYes
Multi-step / tool-chainingYes
Technical referenceView docs
Integration version1.0.0
Last updatedJul 2026

All 4 Okta actions

Users3
create_user
Create a new user in the Okta tenant. The user is activated by default unless ``activate`` is set to false.
get_user
Fetch a single Okta user by ID, login, or email address.
update_user
Update the profile of an existing Okta user. Only the fields you pass are changed; the existing profile is merged with your updates server-side.
Type ID Options1
list_type_id_options
List the available user-type options for the tenant (``GET /meta/types/user``). Useful to discover valid ``type_id`` values for create_user / update_user.

See full parameters and response schemas in the Okta integration docs

Two ways to use Okta in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Okta action and runs it. No workflow to build.
Compose a workflowNeed it to happen every time? Describe the process and the composer wires Okta into a repeatable workflow you can run on a schedule, from chat, or as an API.

Connecting Okta

CustomOkta uses a custom authentication flow. ModuleX encrypts whatever credentials you supply and scopes them to your organization.

Step-by-step setup in the Okta docs

Works with Okta

Agents often chain Okta with these. Connect them once and one agent can use all of them in a single task.

Okta + ModuleX FAQ

  • A ModuleX agent can run any of Okta's 4 actions, across users and type id options, from a plain-English request, using your organization's own Okta credentials.

Put Okta to work in ModuleX.

Connect Okta once with your own credentials and let your agent run all 4 actions on demand.

Last updated: Jul 2026Browse all 179 integrations