Get Application
okta.get_app
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
Fetch one Okta app integration by id, with its status and sign-on mode.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Okta
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- org_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
app_id The Okta application id to act on. | string | Yes | — | — | 0oa1a2b3c4D5e6F7g8h9 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"app_id": "0oa1a2b3c4D5e6F7g8h9"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The Okta application id. | string | — |
name The app integration's catalog name, such as 'oidc_client'. | string | — |
label The display label an administrator gave the app. | string | — |
status Whether the app is ACTIVE or INACTIVE. | string | — |
signOnMode The app's sign-on mode, such as SAML_2_0 or OPENID_CONNECT. | string | — |
{
"id": "",
"label": "",
"name": "",
"signOnMode": "",
"status": ""
}See Get Application run in a workflow.
In a technical demo we add the Okta connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.