All integrationsIdentity & Access

Okta

Manage the people in your Okta org: create and update users, run them through the joiner-mover-leaver lifecycle, organise them into groups, and read the System Log.

actions
23
triggers
5

Triggers

Start a workflow when something happens in Okta.

  • New userRuns for each user created in Okta, by an admin, an import or a connected directory, with their login, name and who created them. Add a Get user step for the rest of their profile. Changes made before the workflow is turned on don't start it.
  • User deactivatedRuns each time an Okta user is deactivated, which removes their access to every app, with their login, name and email, who deactivated them, and their manager's name and email when Okta can find them. Add a Get user step for the rest of their profile. Changes made before the workflow is turned on don't start it.
  • User suspendedRuns each time an Okta user is suspended, so they can't sign in but keep their apps and groups, with their login, name and email, who suspended them, and their manager's name and email when Okta can find them. Add a Get user step for the rest of their profile. Changes made before the workflow is turned on don't start it.
  • User locked outRuns each time Okta locks someone out after too many failed sign-ins, with their name, email and login, and their manager's name and email when Okta can find them, so a ticket or a note to their manager needs no lookup step. Lockouts from before the workflow is turned on don't start it.
  • User added to a groupRuns each time someone is added to an Okta group you choose, by an admin or a group rule, with their login, name and who added them. Add a Get user step for the rest of their profile. Changes made before the workflow is turned on don't start it.

Actions

Steps a workflow can run in Okta.

  • List usersList users in your Okta org, one page at a time (up to 200 a page), optionally narrowed by status or by a search across name, email and login. Each comes with their name, email, status and last sign-in ready to show. Beta: turn on Read every page to get everyone in one step. To find people who haven't signed in for a while, use "List users who haven't signed in" instead.
  • List users who haven't signed inBeta. List the Okta users who haven't signed in for a number of days (inactive, dormant or unused accounts), ready for a report or an approval: each person's name, email, last sign-in date and days since, longest first, with a count. Okta cannot search by last sign-in, so this reads every page of users itself and keeps the ones that match: no loop, filter or paging steps needed. Active users are checked unless you pick another status. People who have never signed in are included and marked.
  • Get userFetch one Okta user: their name, email, status and last sign-in ready to show, with their full profile and credential metadata.
  • Create userCreate a user in your Okta org. Left unactivated they are staged and cannot sign in; activated without a password Okta emails them an activation link.
  • Update userUpdate a user's profile. Only the fields you fill in change; everything else is left as it is.
  • Activate userActivate a staged or deactivated user. With the email off, Okta returns the activation link instead of sending it.
  • Deactivate userDeactivate a user, removing their access to every assigned app. This is the offboarding step, and it cannot be undone except by reactivating them.
  • Suspend userSuspend an active user. They cannot sign in but keep every group and app assignment, so this is reversible.
  • Unsuspend userReturn a suspended user to active so they can sign in again.
  • Reset passwordHave Okta email a user a link to choose a new password. Until they use it they can't sign in, so only do this when they're expecting the email.
  • Unlock userUnlock a user Okta locked out after too many failed sign-ins, so they can sign in again with their current password.
  • Revoke user sessionsSign a user out of Okta everywhere, forcing them to authenticate again. The first move on a compromised account.
  • Delete userPermanently delete a user. Okta only deletes a deactivated user, so an active one is deactivated first, which cannot be recovered.
  • List a user's groupsList every group a given user is a member of.
  • List groupsList groups in your Okta org, optionally narrowed by type or by a search across name and description.
  • Get groupFetch one Okta group's name, description and type.
  • Create groupCreate an Okta group. Groups made this way are Okta groups, the only kind whose membership an API can change.
  • Update groupReplace an Okta group's name and description. Okta has no partial update for groups, so a description left blank is cleared; read the group first if you mean to keep it.
  • Delete groupDelete an Okta group. Its members keep their accounts; only the group and its assignments go.
  • List group membersList the users who belong to a given Okta group.
  • Add user to groupAdd a user to an Okta group. Safe to re-run, because Okta accepts it whether or not they were already a member.
  • Remove user from groupRemove a user from an Okta group. Their account is untouched; they lose only what the group granted.
  • List System Log eventsRead your org's audit trail: sign-ins, lifecycle changes, admin actions. Okta keeps 90 days.

Automate Okta with Lodol.

Connect Okta, then hand Lodol the job in Slack, Claude or ChatGPT.

Free plan, no credit card