List User Groups

okta.list_user_groups
ActionBusiness appsconnection required

Calls the Okta API with the connection's credentials.

List every group a user belongs to, including their app groups.

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, 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
max_pages
How many 'rel=next' Link-header pages to follow before stopping and reporting a cursor.
numberNo1≥ 1—

Example configuration

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

{
  "max_pages": 1,
  "user_id": "00u1a2b3c4D5e6F7g8h9"
}

Output

One shape.

result

FieldTypeExample
items
The records Okta returned across the pages that were read.
array—
count
How many records are in 'items'.
number—
pages
How many pages were actually fetched.
number—
next_url
The 'rel=next' URL Okta sent for the following page; empty when the read finished.
string—
next_after
The 'after' cursor taken from 'next_url'; feed it back in as 'after' to continue.
string—
{
  "count": 0,
  "items": [],
  "next_after": "",
  "next_url": "",
  "pages": 0
}

Notes

  • Okta paginates with a Link header, not a body field; 'next_after' carries the cursor.
  • Okta sends a 'rel=next' link even on a final page, so paging stops on an empty page.
  • Okta declares no page size or cursor on this endpoint, so it takes neither.

See List User Groups 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.