Book a demo

Get User

okta.get_user
ActionBusiness appsconnection required

Calls the Okta API with the connection's credentials.

Fetch one Okta user by id, by login, or by login shortname, with their current lifecycle status.

Ask about OktaAll Okta nodesProvider API docs ↗

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Okta
Secret shape
the API token, or {"api_token": "…"}
Config it needs
org_url
Resolved by
config.connection_id, else node.connection_id

Configuration

1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
user_id
The user to act on — an Okta user id, their login, or the login shortname.
stringYes——00u1a2b3c4D5e6F7g8h9

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "user_id": "00u1a2b3c4D5e6F7g8h9"
}

Output

One shape.

result

FieldTypeExample
id
The Okta user id.
string—
status
The user's lifecycle status, such as STAGED, ACTIVE or SUSPENDED.
string—
created
When Okta created the user, as an ISO 8601 timestamp.
string—
activated
When the user was activated, as an ISO 8601 timestamp.
string—
profile.login
The user's Okta login, normally their email address.
string—
profile.email
The user's primary email address.
string—
profile.firstName
The user's given name.
string—
profile.lastName
The user's family name.
string—
{
  "activated": "",
  "created": "",
  "id": "",
  "profile": {
    "email": "",
    "firstName": "",
    "lastName": "",
    "login": ""
  },
  "status": ""
}

Related Okta nodes

See Get User run in a workflow.

In a technical demo we add the Okta connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demoTalk to sales