ActionOktaUpdated June 2026

How do I create an Okta user?

Short answer: You can create okta user in Okta by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Okta Create Okta User action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Okta User in Okta — start free All 3 Okta actions

Create Okta User in Okta — start free

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
First Name firstName	string	Required	Contact's first (given) name.
Last Name lastName	string	Required	Contact's last (family) name.
Email email	email	Required	The email address. Used as the recipient or identifier depending on context.
Login login	string	Required	Usually the email address
Activate Immediately activate	boolean	Optional	Activate Immediately

Sample request

{
  "firstName": "e.g. Jane",
  "lastName": "e.g. Doe",
  "email": "e.g. user@example.com",
  "login": "{{trigger.login}}",
  "activate": "{{trigger.activate}}"
}

Returns

{
  "id": "00u456",
  "status": "STAGED",
  "profile": {
    "email": "john@example.com",
    "lastName": "Doe",
    "firstName": "John"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Okta User.

What does the Create Okta User action do in Okta?

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.

What inputs does Create Okta User require?

Required: First Name, Last Name, Email, Login. Every input accepts a static value or a variable from any upstream node in your workflow.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Okta User support batch operations?

Yes. Run Create Okta User inside a Loop node to process arrays. TinyCommand handles Okta's rate limits automatically so you don't have to throttle manually.

How do I create an Okta user?

The fields this action accepts.

Apps that pair well as the trigger for Create Okta User.

Questions about Create Okta User.

Other Okta actions.