Create User
okta.create_user
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
Create a user in the Okta org, optionally activating them and adding them to groups in the same call.
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
10 fields, none 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 |
|---|---|---|---|---|---|
email The new user's primary email address; it is also used as the login when 'login' is left blank. | string | No | — | email format | — |
login The Okta login for the new user, when it differs from their email address. | string | No | — | — | — |
first_name The new user's given name. | string | No | — | — | — |
last_name The new user's family name. | string | No | — | — | — |
mobile_phone The new user's mobile phone number, in the format the org expects. | string | No | — | — | — |
profile The full Okta profile object, for orgs with a customised user schema; the individual name and email fields are merged into it. | object | No | — | — | — |
credentials Okta's credentials object, for example a password or a recovery question. Reference a stored value with an expression rather than typing a secret. | object | No | — | credential material | credential |
group_ids Okta group ids the new user should be added to as part of creation. | array | No | — | array of string | — |
activate Activate the user immediately; when false Okta leaves them STAGED. | boolean | No | true | — | — |
next_login Set to changePassword to make the user choose a new password at first sign-in; leave blank otherwise. | string | No | — | one of "changePassword" | — |
- At least one of email, profile must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"activate": true
}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 Create 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.