ActionOktaUpdated September 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.

Triggered by

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

Any of these apps can fire this action as part of a workflow.

2 Google Sheets triggers

HubSpot → Okta

18 HubSpot triggers

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 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 Create Okta User support batch operations?

Run Create Okta User 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

Get 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.

Action

List Okta Users

Paginated users with filters. For sync workflows that mirror Okta to other directories or for "audit who has access to X" reporting.

Create Okta User in Okta — start free