Update User
okta.update_user
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
Change a user's profile or credentials. The default partial mode merges the keys you send; replace mode overwrites the whole profile.
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
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
user_id The user to act on — an Okta user id, their login, or the login shortname. | string | Yes | — | — | 00u1a2b3c4D5e6F7g8h9 |
profile The profile attributes to change, as a JSON object of Okta profile keys; at least one key, since an empty object changes nothing. | object | No | — | ≥ 1 characters | {"department":"Platform","title":"Staff Engineer"} |
credentials Okta's credentials object, for a password or recovery-question change; at least one key, since an empty object changes nothing. | object | No | — | ≥ 1 characters; credential material | credential |
mode partial merges the keys you send (POST); replace overwrites every profile attribute with what you send (PUT). | string | No | partial | one of "partial", "replace" | — |
- At least one of profile, credentials must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"mode": "partial",
"profile": {
"department": "Platform",
"title": "Staff Engineer"
},
"user_id": "00u1a2b3c4D5e6F7g8h9"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
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": ""
}See Update 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.