ActionOktaUpdated September 2026
How do I list Okta users?
Short answer: You can list okta users in Okta by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Okta List Okta Users action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Search search | string | Optional | Search. e.g. "profile.email eq "john@example.com"" |
Limit limit | number | Optional | Limit |
Sample request
{"search": "profile.email eq \"john@example.com\"","limit": "{{trigger.limit}}"}
Returns
[{"id": "00u123","status": "ACTIVE","profile": {"email": "john@example.com","login": "john@example.com","lastName": "Doe","firstName": "John"}}]
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Okta Users.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Okta Users.
What does the List Okta Users action do in Okta?
Paginated users with filters. For sync workflows that mirror Okta to other directories or for "audit who has access to X" reporting.
What inputs does List Okta Users require?
List Okta Users has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Okta returns an error?
The run history shows the failed step with its input and the error message Okta returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Okta Users support batch operations?
Run List Okta Users inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Okta's rate limits.
More actions
Other Okta actions.
Action
Create Okta User
Provisions a new user with profile, optional immediate activation. The standard hook for "new hire from ATS → provision in Okta with the right group memberships" onboarding workflows.
ActionGet Okta User
Returns a user by ID or login with profile, status, group memberships. The standard lookup for "is this user active in Okta?" pre-flight checks.