Add User to Group
okta.add_user_to_group
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
Add a user to an Okta group, granting them everything that group is assigned. Adding a member who is already in the group is not an error.
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 |
|---|---|---|
added True once Okta accepted the membership. | boolean | — |
group_id The group the user was added to. | string | — |
user_id The user that was added. | string | — |
{
"added": false,
"group_id": "",
"user_id": ""
}Notes
- Okta only lets memberships be changed on groups of the OKTA_GROUP type; an APP_GROUP is owned by the app import that created it.
See Add User to 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.