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).

Put Okta to work View Okta integration docs

Overview

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.

Ask the assistant

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

Use cases

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

At a glance

Okta integration at a glance

VendorOkta

CategoryDeveloper Tools & Infrastructure

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 updatedJun 2026

Reference

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

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.

Security

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

Pairs well with Okta

Agents often chain Okta with these — connect them once and the agent can use all of them in a single task.

FAQ

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.

No. The agent selects the right Okta action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through a secure Okta connection; your credentials are stored encrypted and scoped to your organization.

4, spanning users and type id options.

Okta runs on your own credentials, so any Okta usage is billed by Okta directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Okta to work in ModuleX.

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

Put Okta to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →