Remove User from Application

okta.remove_app_user
ActionBusiness appsconnection required

Calls the Okta API with the connection's credentials.

Unassign a user from an app integration, removing the access it granted. A user who also has the app through a group keeps it.

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, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
app_id
The Okta application id to act on.
stringYes——0oa1a2b3c4D5e6F7g8h9
user_id
The Okta user id to act on; this endpoint does not accept a login in place of the id.
stringYes——00u1a2b3c4D5e6F7g8h9
send_email
Ask Okta to send the deprovisioning email for this application.
booleanNofalse——

Example configuration

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

{
  "app_id": "0oa1a2b3c4D5e6F7g8h9",
  "send_email": false,
  "user_id": "00u1a2b3c4D5e6F7g8h9"
}

Output

One shape.

result

FieldTypeExample
removed
True once Okta accepted the unassignment.
boolean—
app_id
The application the user was removed from.
string—
user_id
The user that was removed.
string—
{
  "app_id": "",
  "removed": false,
  "user_id": ""
}

See Remove User from Application 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.