Delete User

okta.delete_user
ActionBusiness appsconnection required

Calls the Okta API with the connection's credentials.

Permanently delete a user. Okta only deletes a user who is already DEPROVISIONED, so run Deactivate User first or switch on 'deactivate_first' and this node will make both calls in order. Deletion cannot be undone.

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

3 fields, 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
deactivate_first
Deactivate the user before deleting them, which is what Okta requires for a user who is still active.
booleanNofalse——
send_email
Send Okta's deactivation email when this node deactivates the user.
booleanNofalse——

Example configuration

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

{
  "deactivate_first": false,
  "send_email": false,
  "user_id": "00u1a2b3c4D5e6F7g8h9"
}

Output

One shape.

result

FieldTypeExample
deleted
True once Okta accepted the deletion.
boolean—
user_id
The user that was deleted.
string—
deactivated
True when this node deactivated the user before deleting them.
boolean—
{
  "deactivated": false,
  "deleted": false,
  "user_id": ""
}

Notes

  • A delete against a user Okta has not deprovisioned does not remove them.

See Delete 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.