Integration · Security and identity
AI agents for Okta
Find people and read their groups, apps, MFA factors and sign-in history in Okta, list groups and members, and run joiner and leaver steps.
- Actions
- 14
- Read
- 8
- Write
- 6
Actions
What your agents can do in Okta
Find people and read their groups, apps, MFA factors and sign-in history in Okta, list groups and members, and run joiner and leaver steps: create a user, add or remove group membership, unlock, deactivate, or reset MFA factors.
Read 8
Look things up. Nothing changes.
Find users
Finds people.
Get a user
Reads one person by Okta ID or login (usually their email): id, status, created, activated, statusChanged, lastLogin, lastUpdated, passwordChanged, type and the full profile.
List a user's groups
Lists the groups a person belongs to.
List a user's apps
Lists the apps assigned to a person (their Okta dashboard tiles).
List a user's MFA factors
Lists the MFA factors a person has enrolled.
Find groups
Lists groups, by name prefix (q) or an expression (search, like profile.name sw "Eng" or type eq "APP_GROUP").
List a group's members
Lists the people in a group.
Search the system log
Reads Okta's audit log: sign-ins, MFA challenges, lockouts, admin changes.
Write 6
Create, change or send.
Create a user (write)
WRITE: creates a person in Okta with a first name, last name, email and login.
Add a user to a group (write)
WRITE: adds a person to an Okta group (OKTA_GROUP only), which can give them the group's apps.
Remove a user from a group (write)
WRITE: removes a person from an Okta group, which can take away the group's apps.
Unlock a user (write)
WRITE: unlocks a person whose status is LOCKED_OUT after too many failed sign-ins, so they can sign in with their current password.
Deactivate a user (write)
WRITE, for leavers: deactivates a person.
Reset all MFA factors (destructive)Deletes data
DESTRUCTIVE: removes every MFA factor a person has enrolled (push, authenticator apps, phone, security keys).
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Okta account.
What you enter
- API token
Settings
- Okta org address
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Okta data
Ask a question in plain words. The agent can find users, get a user or list a user's groups in Okta, then answers with what it found.
- 02
Let an agent update Okta
Have the agent create a user or add a user to a group in Okta as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Okta and Slack: it can find users in Okta and post a summary to a Slack channel in the same run.
Works well with
More Security and identity tools
- Microsoft Entra ID10 actionsFind people and groups in Microsoft Entra ID (formerly Azure Active Directory), read a person's group and role memberships and their sign-in log, add or remove group members, and run leaver and incident steps.
- Google Workspace Admin9 actionsManage people and groups in a Google Workspace domain.
- CrowdStrike Falcon8 actionsInvestigate and respond in CrowdStrike Falcon: search the hosts the Falcon sensor protects and read their details, network-contain a compromised host or lift containment, search and read alerts.
- Wiz7 actionsWork cloud security issues in Wiz: list open issues by severity or type, read one issue with the affected resource and its notes, move it to in progress, resolve or reject it with a reason, add a note.
- Vanta8 actionsTrack compliance in Vanta: see which automated tests are failing and the exact resources (users, buckets, laptops, repos) causing it, progress on each framework.
- 1Password4 actionsWatch a 1Password Business account's security activity through the Events API.
FAQ
Okta and MyDeepAgents
Can MyDeepAgents connect to Okta?
Yes. The Okta connector has 14 actions: 8 read and 6 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Okta?
Paste an API key from your Okta account. You'll need: API token. The connection also asks for: Okta org address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Okta without asking?
Only if you let it. Each of the 6 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Okta in workflows as well as agents?
Yes. Every Okta action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Okta to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.