- Integrations
- /
- Okta
Okta
Okta identity user management
Okta is the enterprise identity-and-access management platform — single sign-on, multi-factor auth, lifecycle management, and the identity hub that authenticates users across all the SaaS apps the company uses. Tiny Command exposes three actions, no triggers (Okta supports Event Hooks configured in admin pointing at a webhook URL; for "react to user-created, user-deactivated" workflows, configure Event Hooks at a Tiny Command webhook trigger URL): List Users (paginated org users with filters), Get User (full user record with profile, status, group memberships), Create User (provision a new user with profile, optional password, optional immediate activation). The connection uses an Okta API token from Admin → API → Tokens, scoped to the connected admin user's permissions. The Create User pattern is the workflow shape for onboarding: when an Ashby/Workable hire fires, Create User in Okta with the new employee's profile, add them to appropriate groups (which entitles them to apps via group-based assignments), trigger MFA enrollment via email.
Do anything Okta can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| 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. |
| 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. |
Pre-built Okta workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Okta once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Okta field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Okta integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Okta to Tiny Command?
What Okta triggers does Tiny Command support?
What Okta actions can I run from a workflow?
Is the Okta integration real-time?
Do I need to write code to use Okta with Tiny Command?
How much does the Okta integration cost?
More other apps people connect.
Same category as Okta, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Okta.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.