Remove User from Group
okta.remove_user_from_group
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
Remove a user from an Okta group, withdrawing the access it granted.
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, 2 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 |
|---|---|---|---|---|---|
group_id The Okta group id to act on. | string | Yes | — | — | 00g1a2b3c4D5e6F7g8h9 |
user_id The Okta user id to act on; this endpoint does not accept a login in place of the id. | string | Yes | — | — | 00u1a2b3c4D5e6F7g8h9 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"group_id": "00g1a2b3c4D5e6F7g8h9",
"user_id": "00u1a2b3c4D5e6F7g8h9"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
removed True once Okta accepted the removal. | boolean | — |
group_id The group the user was removed from. | string | — |
user_id The user that was removed. | string | — |
{
"group_id": "",
"removed": false,
"user_id": ""
}See Remove User from Group 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.