Activate User
okta.activate_user
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
Activate a STAGED or DEPROVISIONED user. When the activation email is not sent, Okta returns the activation URL and token so a workflow can deliver them itself.
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
2 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 |
send_email Let Okta email the activation link; turn this off to receive the activation URL in this node's output instead. | boolean | No | true | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"send_email": true,
"user_id": "00u1a2b3c4D5e6F7g8h9"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
activated True once Okta accepted the activation. | boolean | — |
user_id The user that was activated. | string | — |
activationUrl The activation link Okta returns when it did not send the email. | string | — |
activationToken The one-time activation token behind that link, when Okta returned one. | string | — |
{
"activated": false,
"activationToken": "",
"activationUrl": "",
"user_id": ""
}See Activate 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.