Short answer: Drop the "Okta → Get Okta User" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
User ID or Login userId | string | Required | User ID or Login. e.g. "john@example.com or 00u123" |
{"userId": "john@example.com or 00u123"}
{"id": "00u123","status": "ACTIVE","profile": {"email": "john@example.com","lastName": "Doe","firstName": "John"},"credentials": {"provider": {"type": "OKTA"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.