Okta

Overview

Authorizing an Account

Authorize an account from the current Okta org

This procedure explains how to create a new connection for your current Okta org. This is the Okta org you used to launch this Workflows environment.

If you want to create a new connection for a different Okta org, see the section Authorize an account from another Okta org below.

Requirements

To perform this procedure:

You must be assigned to the Okta Workflows OAuth app.
You must have Super Admin credentials.

You also need the following information for authorizing your Okta account:

Domain: Your Okta org domain. If the URL of your Okta org is https://yourcompany.okta.com, then your domain is yourcompany.okta.com.
Client ID and Client Secret: The client ID and client secret from your Okta Workflows OAuth app. To find this, go to Okta Admin Console > Applications > Okta Workflows OAuth app > Sign On tab > Sign On Methods.

Procedure

Back in Okta Workflows Console,

Go to Settings.
Click +New Connection. All available connectors appear.
Select the Okta connector. New Connection window appears.
In the New Connection window, enter the Connection Nickname. This is the display name you want to appear in your list of connections.
Enter Domain, Client ID, and Client Secret.
Click Create. The new connection appears in the Connections list.

Authorize an account from another Okta org

This procedure explains how to create a new connection for an Okta org different from your current org.

If you want to create a new connection for the current Okta org, see the section Authorize an account from the current Okta org.

This task includes the following procedures:

Create an OpenID Connect web app in the target Okta org
Configure the OpenID Connect web app
Authorize an account from the target Okta org

1. Create an OpenID Connect web app in the target Okta org

In the Okta Admin console of your target Okta org,

Go to Applications > Applications > Add Application.
Click Create New App. Create New App pop-up window appears.
In the window, select Platform as Web and Sign-on Method as OpenID Connect. Create OpenID Connect Integration page appears.
On the page, enter your Application name. This is the app display name.
Enter a Login Redirect URI for the app. The URI depends on the domain of your Workflows instance. For example, if your Workflow URI is https://designer.ui.workflow.oktapreview.com, then your redirect URI is https://designer.ui.workflow.oktapreview.com/app/oauth/okta/authorize.
Click Save.

The app is created and appears on the Applications page.

2. Configure the OpenID Connect web app

In the Okta Admin console,

Go to Applications > Applications.
Select your newly created application.
On the General tab, click Edit.
In the Allowed Grant Types list, select Refresh Token.
Click Save.
Select the Assignments tab, and then click Edit.
Assign the app to the appropriate users. You can assign it to individual people or to groups. Note: The user must be a Super Admin.
Save your assignments.
On the Okta API Scopes tab, grant consent for the scopes required for your use cases.
Click Save.

The app is now configured and an assigned user can create a new connection for this org.

3. Authorize an account from the target Okta org

Requirements

To perform this procedure:

You must be assigned to the OpenID Connect web app created in the previous procedures.
You must have Super Admin credentials.

You also need the following information for authorizing your Okta account:

Domain: Your Okta org domain. If the URL of your Okta org is https://yourcompany.okta.com, then your domain is yourcompany.okta.com.
Client ID and Client Secret: The client ID and client secret from your OAuth2 app. To find this, go to Okta Admin Console > Applications > Your OpenID Connect web app > Sign On tab > Sign On Methods.

Back in the Okta Workflows Console,

Go to Settings.
Click +New Connection. All available connectors appear.
Select the Okta connector. New Connection window appears.
In the New Connection window, enter the Connection Nickname. This is the display name you want to appear in your list of connections.
Enter Domain, Client ID, and Client Secret.
Click Create.

The new connection appears in the Connections list.

Events

User Activated
Trigger a Flow when a user is activated in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time that the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service.
- Version: versioning indicator
- Admin (object): Okta admin who provisioned the user
  
  ID: ID of the Okta Admin
  
  Alternate ID: email address of the Okta Admin
  
  Display Name: display name of the Okta Admin
- Okta User (object): the Okta user who was added to the application
  
  ID: ID of the Okta user
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- UUID: webhook event’s universal unique identified
- Full Details (object): entire raw JSON payload returned from the Okta API
User Assigned to Application
Trigger a Flow when a user is assigned to an application in Okta.

Unless otherwise indicated, field types are text.

Options
- Application (drop-down list): Choose from a list of existing applications in your Okta organization.
- Application Instance (drop-down list): Choose from a list of existing application instances, dependent on the Application chosen in the previous step.
  
  Note: This event will only trigger for the selected application instance.
Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service.
- Version: versioning indicator
- Admin (object): Okta admin who provisioned the user
  
  ID: ID of Okta admin who provisioned the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was added to the application
  
  ID: ID of the Okta user who was added to the application
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- Application User (object): target application’s user details
  
  ID: user’s ID in the target application
  
  Alternate ID: user’s alternate ID in the target application (usually their email address)
  
  Display Name: display name of the Okta user
- Application (object): target application
  
  ID: ID of the target application
  
  Alternate ID: alternate ID of the target application
  
  Display Name: display name of the target application
- User Groups (list of objects): if the user is a member of multiple groups, the following fields are returned for each group
  
  ID: ID of the group that the user belongs to
  
  Name: name of the group that the user belongs to
  
  Description: description of the group that the user belongs to
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
User Added to Group
Trigger a Flow when a user is assigned to a group in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who provisioned the user
  
  ID: ID of Okta admin who provisioned the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was added to the group
  
  ID: ID of the Okta user who was added to the group
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- Group (object): target group that the user was assigned to
  
  ID: ID of the target group
  
  Alternate ID: alternate ID of the target group
  
  Display Name: display name of the target group
- User Groups (list of objects): if the user is a member of multiple groups, the following fields are returned for each group
  
  ID: ID of the group that the user belongs to
  
  Name: name of the group that the user belongs to
  
  Description: description of the group that the user belongs to
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
User Created
Trigger a Flow when a user is assigned to an application in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who created the user
  
  ID: ID of Okta admin who created the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was created
  
  ID: ID of the Okta user who was created
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
User Deactivated
Trigger a Flow when a user is deactivated in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who deactivated the user
  
  ID: ID of Okta admin who deactivated the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was deactivated
  
  ID: ID of the Okta user who was deactivated
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
User Deleted
Trigger a Flow when a user is deleted in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object: Okta admin who deleted the user
  
  ID: ID of Okta admin who deleted the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was deleted
  
  ID: ID of the Okta user who was deleted
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
User Unassigned from Application
Trigger a Flow when a user is unassigned from an application in Okta.

Unless otherwise indicated, field types are text.

Options
- Application (drop-down list): Choose from a list of existing applications in your Okta organization.
- Application Instance (drop-down list): Choose from a list of existing application instances, dependent on the Application chosen in the previous step.
  
  Note: This event will only trigger for the selected application instance.
Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who unassigned the user
  
  ID: ID of Okta admin who unassigned the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was unassigned from the application
  
  ID: ID of the Okta user who was unassigned from the application
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- Application User (object): target application’s user details
  
  ID: user’s ID in the target application
  
  Alternate ID: user’s alternate ID in the target application (usually their email address)
  
  Display Name: display name of the Okta user
- Application (object): target application
  
  ID: ID of the target application
  
  Alternate ID: alternate ID of the target application
  
  Display Name: display name of the target application
- User Groups (list of objects): if the user is a member of multiple groups, the following fields are returned for each group
  
  ID: ID of the group that the user belongs to
  
  Name: name of the group that the user belongs to
  
  Description: description of the group that the user belongs to
  
  UUID: webhook event’s universal unique identifier
  
  Full Details (object): entire raw JSON payload returned from the Okta API
User Removed from Group
Trigger a Flow when a user is removed from a group in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who unassigned the user
  
  ID: ID of Okta admin who unassigned the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was unassigned from the group
  
  ID: ID of the Okta user who was unassigned from the group
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- Group (object): target group that the user was unassigned from
  
  ID: ID of the target group
  
  Alternate ID: alternate ID of the target group
  
  Display Name: display name of the target group
- User Groups (list of objects): if the user is a member of multiple groups, the following fields are returned for each group
  
  ID: ID of the group that the user belongs to
  
  Name: name of the group that the user belongs to
  
  Description: description of the group that the user belongs to
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
Suspicious Activity Reported
Trigger a Flow when suspicious activity is reported in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the webhook event was published
- Name: name of the user who reported suspicious activity
- Email: email address of the user
- User ID: ID of the user
- Suspicious Activity Details: details about the suspicious activity reported
- Full Details (object): entire raw JSON payload returned from the Okta API
User Suspended
Trigger a Flow when a user is suspended in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who suspended the user
  
  ID: ID of Okta admin who suspended the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was suspended
  
  ID: ID of the Okta user who was suspended
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
User Unsuspended
Trigger a Flow when a user is unsuspended in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who unsuspended the user
  
  ID: ID of Okta admin who unsuspended the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
- Okta User (object): Okta user who was unsuspended
  
  ID: ID of the Okta user who was unsuspended
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
Custom Webhook
Choose an event hook and listen for the specified event in Okta that will trigger the Flow in real time.

Unless otherwise indicated, field types are text.

Options
- Event (drop-down list): Choose from a list of event types. The event types in this list directly correspond to the events in the Event Type Catalog Documentation.
Output
- Output
  
  Date and Time: date and time that the event was triggered in Okta
  
  Message: message details about the event
  
  Event ID: event’s unique identifier key
  
  Event Type: type of event that was published
  
  Event Time: timestamp when the notification was delivered to the service
  
  Version: versioning indicator
  
  Actor (object): Okta user who performed the event operation
  
  ID: ID of the Okta user
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
  
  Targets (list of objects): Okta resources that were operated on (Users, Groups, Applications, Application Users, or others)
  
  ID: ID of the Okta resource
  
  Alternate ID: alternate ID of the Okta resource
  
  Display Name: display name of the Okta resource
  
  UUID: webhook event’s universal unique identified
  
  Full Details (object): entire raw JSON payload returned from the Okta API
User Reactivated
Trigger a Flo when a user is reactivated in Okta.

Unless otherwise indicated, field types are text.

Output
- Date and Time: date and time the event was triggered in Okta
- Message: message details about the event
- Event ID: event’s unique identifier key
- Event Type: type of event that was published
- Event Time: timestamp when the notification was delivered to the service
- Version: versioning indicator
- Admin (object): Okta admin who reactivated the user
  
  ID: ID of Okta admin who deactivated the user
  
  Alternate ID: email address of the Okta admin
  
  Display Name: display name of the Okta admin
  
  Type: type of the Okta admin
- Okta User (object): Okta user who was deactivated
  
  ID: ID of the Okta user who was deactivated
  
  Alternate ID: email address of the Okta user
  
  Display Name: display name of the Okta user
  
  Type: type of the Okta user
- UUID: webhook event’s universal unique identifier
- Full Details (object): entire raw JSON payload returned from the Okta API
Context
- Execution ID: unique identifier associated with the execution of the Flo

Actions

Create User
Create a new user in Okta. This action commonly follows an event like User is Added to Application Membership.

Unless otherwise indicated, field types are text.

Options
- Without credentials
- With recovery question
- With password
- With password and recovery questions
- With authentication provider
- In group
For more detail on these options, or additional info regarding creating users in Okta, reference this documentation.

Input

Input fields vary by option but will always include the mandatory Okta profile attributes: First Name, Last Name, Email, and Login. Required fields are indicated by a red asterisk.
- Profile
  
  First Name: first name of the Okta user
  
  Last Name: last name of the Okta user
  
  Email: email address of the Okta user
  
  Login: login of the Okta user, in email address format
  
  Mobile Phone: mobile phone of the Okta user
- Credentials
  
  Question: password recovery question (must be specified if Answer is specified)
  
  Answer: answer to the password recovery question (must be specified if Question is specified)
  
  Password: password that meets minimum criteria (see documentation)
  
  Provider Name: name of the identity provider. Note that you must specify the directory instance name for ACTIVE_DIRECTORY or LDAP providers.
  
  Provider Type (drop-down list): identity provider type
- Activate
  
  Activate (boolean): user is activated upon creation (see documentation)
Output
- Results
  
  Raw Body (object): raw payload returned from the Okta API
  
  ID: ID of the user created in Okta
  
  Status: current status of the user (STAGED, PROVISIONED, ACTIVE, RECOVERY, LOCKED_OUT, PASSWORD_EXPIRED, SUSPENDED, or DEPROVISIONED)
  
  Created (date): timestamp when the user was created
  
  Activated (boolean): timestamp when transition to ACTIVE status completed
  
  Status Changed (date): date that the user’s status changed
  
  Last Login (date): timestamp of the user’s last login date
  
  Last Updated (date): timestamp of the last user update
  
  Password Changed (date): timestamp when password last changed
Custom API Action
Use Custom API Action to make an authenticated request to the Okta API. Reference the Okta API documentation for additional details about working directly with the Okta API.

Options
- Request Type (drop-down): use the appropriate request type depending on the endpoint/method
  
  GET
  
  POST
  
  PUT
  
  PATCH
  
  DELETE
Input
- Relative URL (text): Specify the relative URL as /api/v2/{insert_remaining_URL}. You can specify query parameters in the relative URL using “?”, or specify the query parameters as an object key pair in the Query input.
- Headers (object): Specify any headers required in addition to authorization or content-type (these are already handled by this connector).
- Query (object): Specify any additional query parameters that should be included in object format (key value pairs).
- Body (object): Specify a request body in JSON format. Only available for POST, PUT, and PATCH requests.
Output
- Response
  
  Status Code (number): status code returned by the Okta API
  
  Headers (object): HTTP headers returned by the Okta API
  
  Body (object): body of the response returned from Okta API
Delete User
Delete a deactivated Okta user by ID. If you use this action on an Okta user who is active, the user will be deactivated. A second Delete User action is required.

Input
- User
  
  ID (text): ID of the Okta user
  
  Send Email? (boolean): send a deactivation email to the administrator if true
Output
- Status Code (number): status code returned by the API:
  
  204: Successful deactivation/deletion
  
  404: Invalid ID–either the ID is incorrect or that user has already been deleted
Read Group
Read an Okta group’s information by ID.

Unless otherwise indicated, field types are text.

Input
- Group
  
  ID: ID of the Okta group
Output
- Properties
  
  ID: ID of the Okta group
  
  Created: timestamp when the group was created
  
  Last Updated: timestamp when the group was last updated
  
  Last Membership Updated: timestamp when the group’s memberships were last updated
  
  Object Class (list of text): determiner of the group’s profile
  
  Type: how the group’s profile and memberships are managed: OKTA_GROUP, APP_GROUP, or BUILT_IN
  
  Profile (object)
  
  Name: name of the group
  
  Description: description of the group
Read User
Read an Okta user’s system information and profile properties by ID or username. Custom added fields are included in the profile properties.

NOTE: This action will not read information about application users (you will receive a 404 error if the user type is invalid or incorrect). If you need details about an application user, use the ‘Custom API Action’ card, and visit the Okta API Documentation for reading assigned users for an application.

Unless otherwise indicated, field types are text.

Input
- User
  
  ID or Login: ID or login username of the Okta user (usually in an email format)
Output
- System Properties
  
  ID: ID of the Okta user
  
  Status: current status of the user: STAGED, PROVISIONED, ACTIVE, RECOVERY, LOCKED_OUT, PASSWORD_EXPIRED, SUSPENDED, or DEPROVISIONED
  
  Created (date): timestamp when the user was created
  
  Activated (boolean): timestamp when transition to ACTIVE status completed
  
  Status Changed (date): date of the user’s last status change
  
  Last Login (date): timestamp of the user’s last login date
  
  Last Updated (date): timestamp of the user’s last update
  
  Password Changed (boolean): timestamp of the user’s last password change
  
  Credentials (list)
  
  Emails (list): list of emails associated with the user
  
  Password (boolean): true if the user has a valid password or imported hashed password, false otherwise
  
  Recovery Question (text): recovery question when a user forgets their password
  
  Provider (object)
  
  Name (text): name of the authentication provider
  
  Type (text): type of authentication provider: OKTA, ACTIVE_DIRECTORY, LDAP, FEDERATION, SOCIAL or IMPORT
- Profile Properties
  
  City: city or locality component of user’s address
  
  Cost center: name of a cost center assigned with the user
  
  Country code: country abbreviation
  
  Department: name of user’s department
  
  Display name: name of the user, suitable for display to end users
  
  Division: name of the user’s division
  
  Primary email: user’s primary email address
  
  Employee number: user’s organizatio- or company-assigned unique identifier
  
  First name: user’s first name
  
  Honorific prefix: user’s honorific prefix(es) or title in most Western languages
  
  Honorific suffix: user’s honorific suffix(es)
  
  Last name: user’s last name or family name
  
  Locale: user’s default location for purposes of localizing items like currency, date/time format, and numerical representations
  
  Username: login username of the user, usually in the form of an email address
  
  Manager: display name of the user’s manager
  
  ManagerId: ID of the user’s manager
  
  Middle name: user’s middle name
  
  Mobile phone: user’s mobile phone number
  
  Nickname: user’s preferred nickname, if applicable
  
  Organization: name of the user’s organization
  
  Postal Address: mailing address component of user’s address
  
  Preferred language: user’s preferred written or spoken languages
  
  Primary phone: primary phone number of user such as home number
  
  Profile Url: URL of user’s online profile (a web page)
  
  Secondary email: secondary email address of user (typically used for account recovery)
  
  State: state or region component of user’s address
  
  Street address: full street address component of user’s address
  
  Time zone: user’s time zone
  
  Title: user’s title, such as Vice President
  
  User type: user’s relationship to the organization, such as Employee or Contractor
  
  Zip code: zip code or postal code component of user’s address
  
  Custom Profile Properties (dynamically generated): additional custom user profile properties that are generated when configuring this card
Search Groups
Search groups with a query. The query performs a starts with match against groups’ name value. You have the option to display the first matching record only or all matching records in a list (up to 300). For more information, review the Okta documentation here.

Unless otherwise indicated, field types are text.

Options
- Option (drop-down list)
  
  First Matching Record: returns a single record
  
  All Matching Records: returns all matching records, in list format
Input
- Query: query string used to find groups by name (for example, to search for groups related to sales, enter a query value of sales)
Output
- Result
  
  First Matching Record:
  
  Raw Body (object): raw payload returned from the Okta API
  
  ID: ID of the group in Okta
  
  Created (date): timestamp when the group was created
  
  Last Updated (date): timestamp of the last group update
  
  Last Membership Updated: timestamp of the last update to group’s memberships
  
  Object Class (list of text): determiner of the group’s profile
  
  Type: how the group’s profile and memberships are managed: OKTA_GROUP, APP_GROUP, or BUILT_IN
  
  Profile (object)
  
  Name: name of the group
  
  Description: description of the group
  
  All Matching Records:
  
  Groups (list of objects): all matching groups with payload similar to above, in list format
Search Users
Search Okta users with a query. The query performs a starts with match against First Name, Last Name, or Email. You have the option to display the first matching record only or all matching records in a list (up to 200). For more information, review the Okta documentation here.

Unless otherwise indicated, field types are text.

Options
- Option (drop-down list)
  
  First Matching Record: returns a single record
  
  All Matching Records: returns all matching records, in list format
Input
- Query: query string used to find records by first name, last name, or email address (for example, to search for Bob Ross, Bob, Ross, bob.ross@okta.com are all valid query terms)
Output
- Result
  
  First Matching Record:
  
  Raw Body (object): raw payload returned from the Okta API
  
  ID: ID of the user created in Okta
  
  Status: current status of the user: STAGED, PROVISIONED, ACTIVE, RECOVERY, LOCKED_OUT, PASSWORD_EXPIRED, SUSPENDED, or DEPROVISIONED
  
  Created (date): timestamp when the user was created
  
  Activated (boolean): timestamp when transition to ACTIVE status completed
  
  Status Changed (date): date of the last user status change
  
  Last Login (date): timestamp of the user’s last login date
  
  Last Updated (date): timestamp of the user’s last update
  
  Password Changed (date): timestamp of the user’s last password change
  
  First Name: user’s first name
  
  Last Name: user’s last name or family name
  
  Mobile Phone: user’s mobile phone number
  
  Second Email: secondary email address of user (typically used for account recovery)
  
  Login: login username of the user (usually in the form of an email address)
  
  Email: user’s primary email address
  
  All Matching Records:
  
  Users (list of objects): all matching users with payload similar to above, in list format
Update User
Update an Okta user’s system information and profile properties by ID or username.

NOTE: This action will not update information about application users (you will receive a 404 error if the user type is invalid or incorrect). If you need to update an application user, use the ‘Custom API Action’ card, and visit the Okta API Documentation for updating application users.

Unless otherwise indicated, field types are text.

Options
- Update Semantics (drop-down list)
  
  Partial: Updates a user’s profile or credentials with partial update semantics. Any properties that are not specified are ignored, and will maintain their current value.
  
  Strict: Updates a user’s profile and/or credentials using strict-update semantics. IMPORTANT: All profile properties must be specified when updating a user’s profile. Any property not specified in the request is set to null.
Input
- User
  
  ID: ID of the Okta user (usually in an email format)
- Profile
  
  City: city or locality component of user’s address
  
  Cost center: name of a cost center assigned with the user
  
  Country code: country abbreviation
  
  Department: name of user’s department
  
  Display name: name of the user, suitable for display to end users
  
  Division: name of the user’s division
  
  Primary email: user’s primary email address
  
  Employee number: user’s organization- or company-assigned unique identifier
  
  First name: user’s first name
  
  Honorific prefix: user’s honorific prefix(es) or title in most Western languages
  
  Honorific suffix: user’s honorific suffix(es)
  
  Last name: user’s last name or family name
  
  Locale: user’s default location for purposes of localizing items like currency, date/time format, and numerical representations
  
  Username: login username of the user, usually in the form of an email address
  
  Manager: display name of the user’s manager
  
  ManagerId: ID of the user’s manager
  
  Middle name: user’s middle name
  
  Mobile phone: user’s mobile phone number
  
  Nickname: user’s preferred nickname, if applicable
  
  Organization: name of the user’s organization
  
  Postal Address: mailing address component of user’s address
  
  Preferred language: user’s preferred written or spoken languages
  
  Primary phone: primary phone number of user such as home number
  
  Profile Url: URL of user’s online profile (a web page)
  
  Secondary email: secondary email address of user (typically used for account recovery)
  
  State: state or region component of user’s address
  
  Street address: full street address component of user’s address
  
  Time zone: user’s time zone
  
  Title: user’s title, such as Vice President
  
  User type: user’s relationship to the organization, such as Employee or Contractor
  
  Zip code: zip code or postal code component of user’s address
  
  Custom Profile Properties (dynamically generated): additional custom user profile properties that are generated when configuring this card
- Credentials
  
  Password: string value for the user’s new password
  
  Recovery Question: question to enable password recovery for the user
  
  Recovery Answer: answer to password recovery question
Output
- System Properties
  
  ID: ID of the Okta user
  
  Status: current status of the user: STAGED, PROVISIONED, ACTIVE, RECOVERY, LOCKED_OUT, PASSWORD_EXPIRED, SUSPENDED, or DEPROVISIONED
  
  Created (date): timestamp when the user was created
  
  Activated (boolean): timestamp when transition to ACTIVE status completed
  
  Status Changed (date): date of the user’s last status change
  
  Last Login (date): timestamp of the uer’s last login date
  
  Last Updated (date): timestamp of the user’s last update
  
  Password Changed (boolean): timestamp of the user’s last password change
  
  Credentials (list)
  
  Emails (list): list of emails associated with the user
  
  Password (boolean): true if the user has a valid password or imported hashed password, false otherwise
  
  Recovery Question: recovery question when a user forgets their password
  
  Provider (object)
  
  Name: name of the authentication provider
  
  Type: type of authentication provider: OKTA, ACTIVE_DIRECTORY, LDAP, FEDERATION, SOCIAL or IMPORT
- Profile Properties
  
  City: city or locality component of user’s address
  
  Cost center: name of a cost center assigned with the user
  
  Country code: country abbreviation
  
  Department: name of user’s department
  
  Display name: name of the user, suitable for display to end users
  
  Division: name of the user’s division
  
  Primary email: user’s primary email address
  
  Employee number: user’s organization- or company-assigned unique identifier
  
  First name: user’s first name
  
  Honorific prefix: user’s honorific prefix(es) or title in most Western languages
  
  Honorific suffix: user’s honorific suffix(es)
  
  Last name: user’s last name or family name
  
  Locale: user’s default location for purposes of localizing items like currency, date/time format, and numerical representations
  
  Username: login username of the user, usually in the form of an email address
  
  Manager: display name of the user’s manager
  
  ManagerId: ID of the user’s manager
  
  Middle name: user’s middle name
  
  Mobile phone: user’s mobile phone number
  
  Nickname: user’s preferred nickname, if applicable
  
  Organization: name of the user’s organization
  
  Postal Address: mailing address component of user’s address
  
  Preferred language: user’s preferred written or spoken languages
  
  Primary phone: primary phone number of user such as home number
  
  Profile Url: URL of user’s online profile (a web page)
  
  Secondary email: secondary email address of user (typically used for account recovery)
  
  State: state or region component of user’s address
  
  Street address: full street address component of user’s address
  
  Time zone: user’s time zone
  
  Title: user’s title, such as Vice President
  
  User type: user’s relationship to the organization, such as Employee or Contractor
  
  Zip code: zip code or postal code component of user’s address
  
  Custom Profile Properties (dynamically generated): additional custom user profile properties that are generated when configuring this card
Add New User to Group
Add a new Okta user to a group.

Unless otherwise indicated, field types are text.

Input
- Group
  
  ID: ID of the Okta group
- User
  
  ID: ID of the Okta user
Output
- Result
  
  Status (number): status code returned by the API:
  
  204: Successful addition
  
  404: Invalid ID–either the ID is incorrect or that user has already been added
Assign User to an App for SSO
Assign a user without a profile to an app for SSO in Okta.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app to which you want to assign the user. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Input
- User
  
  User ID (text): Unique identification of the user.
  
  Scope (dropdown): Select the user’s scope from User, Co-admin, and Admin.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
Output

Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
System Properties
- User ID (text): Unique identification of the user.
- External ID (text): External identification of the user.
- Created (text): Timestamp when the user was created.
- Last Updated (text): Timestamp when the user was last updated.
- Scope (text): Scope of the user.
- Status (text): Current status of the user.
- Status Changed (text): Timestamp when the user’s status was changed.
- Password Changed (text): Timestamp when the user’s password was changed.
- Sync State (text): Current sync state of the user.
- Last Sync (text): Timestamp when the last sync happened.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
Assign User to an App for SSO and Provisioning
Assign a user to an app with credentials and an app-specific profile. Profile mappings defined for the app are first applied before applying any profile properties specified in the request.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app to which you want to assign the user. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Input
- User
  
  User ID (text): Unique identification of the user.
  
  Scope (dropdown): Select the user’s scope from User, Co-admin, and Admin.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
Output

Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
System Properties
- User ID (text): Unique identification of the user.
- External ID (text): External identification of the user.
- Created (text): Timestamp when the user was created.
- Last Updated (text): Timestamp when the user was last updated.
- Scope (text): Scope of the user.
- Status (text): Current status of the user.
- Status Changed (text): Timestamp when the user’s status was changed.
- Password Changed (text): Timestamp when the user’s password was changed.
- Sync State (text): Current sync state of the user.
- Last Sync (text): Timestamp when the last sync happened.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
Clear User Sessions
Remove all active identity provider sessions. This forces the user to authenticate on the next operation. It optionally revokes OpenID Connect and OAuth refresh and access tokens issued to the user.

Required fields are indicated in red.

Input
- User
  
  User ID (text): Unique identification of the user.
  
  Revoke oauthTokens? (true/false): Revoke OAuth tokens if true.
Output
- Status Code (number): Status code returned by the Okta API.
Deactivate User
Deactivate a user in Okta. This operation cannot be performed on users with a DEPROVISIONED status. Deactivation of a user is an asynchronous operation that cannot be recovered.

Options
- Send Email? (drop-down): send a deactivation message to the administrator
  
  Yes
  
  No
For more detail on these options, or additional info regarding deactivating users in Okta, reference this documentation.

Input
- User
  
  ID or Login (string): ID or login of the Okta user. Login is in email address format.
Output
- Response
  
  Status Code (number): status code returned by the API:
  
  200: Successful deactivation
  
  404: Invalid ID–either the ID is incorrect or that user has already been deactivated
Get Assigned User for an App
Fetch a specific user assignment for an app by id.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app for which you want to get the user assignment. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Input
- User
  
  User ID (text): Unique identification of the user.
Output

Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
System Properties
- User ID (text): Unique identification of the user.
- External ID (text): External identification of the user.
- Created (text): Timestamp when the user was created.
- Last Updated (text): Timestamp when the user was last updated.
- Scope (text): Scope of the user.
- Status (text): Current status of the user.
- Status Changed (text): Timestamp when the user’s status was changed.
- Password Changed (text): Timestamp when the user’s password was changed.
- Sync State (text): Current sync state of the user.
- Last Sync (text): Timestamp when the last sync happened.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
Get Users Groups
Retrieve an Okta user’s current group memberships.

Unless otherwise indicated, field types are text.

Input
- User
  
  ID: ID of the Okta user
Output
- Groups (list of objects)
  
  ID: ID of the Okta group
  
  Name: name of the group
  
  Description: description of the group
  
  Created: timestamp when the group was created
  
  Last Updated: timestamp when the group was last updated
  
  Last Membership Updated: timestamp when the group’s memberships were last updated
List Group Members
List the members of an Okta group.

Input
- Group
  
  ID (text): ID of the Okta group.
Output
- Result
  
  Users (list): Okta users in the group.
List Users Assigned to an App
List all assigned users for an app.

Required fields are indicated in red.

The output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app from which you want to remove the user. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Output

Result
- Users
  
  Profile Properties
  
  Formatted (text):
  
  Name (text): User’s full name.
  
  Nickname (text): User’s nickname.
  
  Given Name (text): User’s first name.
  
  Middle Name (text): User’s middle name.
  
  Family Name (text): User’s last name or family name.
  
  Email (text): User’s primary email.
  
  Profile Url (text): URL of the user’s online profile or a web page.
  
  Picture Url (text): URL of the user’s online picture.
  
  Website (text): URL of the user’s website.
  
  Gender (text): User’s gender.
  
  Birthdate (text): User’s birthdate.
  
  Time Zone (text): User’s time zone.
  
  Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
  
  Phone Number (text): User’s primary phone number.
  
  Street Address (text): Full street address component of user’s address.
  
  Locality (text): Locality component of the user’s address.
  
  Region (text): Region component of the user’s address.
  
  Postal Code (text): Zip code or postal code component of user’s address.
  
  Country (text): Country component of the user’s address.
  
  System Properties
  
  User ID (text): Unique identification of the user.
  
  External ID (text): External identification of the user.
  
  Created (text): Timestamp when the user was created.
  
  Last Updated (text): Timestamp when the user was last updated.
  
  Scope (text): Scope of the user.
  
  Status (text): Current status of the user.
  
  Status Changed (text): Timestamp when the user’s status was changed.
  
  Password Changed (text): Timestamp when the user’s password was changed.
  
  Sync State (text): Current sync state of the user.
  
  Last Sync (text): Timestamp when the last sync happened.
  
  Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
List Users With Filter
List users in Okta based on the filter provided.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Result Set (dropdown): Choose from First matching record and All matching records.
Input
- Status (dropdown): Status of the Okta user - STAGED, PROVISIONED, ACTIVE, RECOVERY, LOCKED_OUT, PASSWORD_EXPIRED, SUSPENDED, or DEPROVISIONED.
- Last Updated (text): Timestamp when the user was last updated.
- ID (text): Unique identifier of the user.
- Login (text): Login username of the user (usually in the form of an email address).
- Email (text): User’s primary email address.
- First Name (text): User’s first name.
- Last Name (text): User’s last name or family name.
- Custom Filter (text): Any custom filter you want to add.
Output

Result
- Raw Output (object): Raw output returned by the Okta API.
- ID (text): Unique identifier of the user.
- Status (text): Current status of the user.
- Created (text): Timestamp when the user was created.
- Activated (text): Timestamp when the user was activated.
- Status Changed (text): Timestamp when the user’s status was changed.
- Last Login (text): Timestamp when the user last logged in.
- Last Updated (text): Timestamp when the user was last updated.
- Password Changed (text): Timestamp when the user’s password was changed.
- First Name (text): User’s first name.
- Last Name (text): User’s last name or family name.
- Mobile Phone (text): User’s mobile phone number.
- Second Email (text): User’s secondary email.
- Login (text): Login username of the user (usually in the form of an email address).
- Email (text): User’s primary email address.
List Users With Search
Search for users based on the properties specified in the search parameter.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Result Set (dropdown): Choose from First matching record and All matching records.
Input
- Status (dropdown): Status of the Okta user - STAGED, PROVISIONED, ACTIVE, RECOVERY, LOCKED_OUT, PASSWORD_EXPIRED, SUSPENDED, or DEPROVISIONED.
- Created (text): Timestamp when the user was created.
- Activated (text): Timestamp when the user was activated.
- Status Changed (text): Timestamp when the user’s status was changed.
- Last Updated (text): Timestamp when the user was last updated.
- ID (text): Unique identifier of the user.
- Username (text): Username of the user.
- First Name (text): User’s first name.
- Last Name (text): User’s last name or family name.
- Middle Name (text): User’s middle name.
- Honorific Prefix (text): User’s honorific prefix(es) or title in most Western languages.
- Honorific Suffix (text): User’s honorific suffix(es).
- Primary Email (text): User’s primary email address.
- Title (text): User’s title.
- Display Name (text): User’s display name.
- Nickname (text): User’s nickname.
- Profile Url (text): URL of the user’s online profile or a web page.
- Secondary Email (text): User’s secondary email.
- Mobile Phone (text): User’s mobile phone number.
- Primary Phone (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address
- City (text): City or locality component of user’s address
- State (text): State or region component of user’s address
- Zip Code (text): Zip code or postal code component of user’s address
- Country Code (text): Country abbreviation
- Postal Address (text): Mailing address component of user’s address
- Preferred Language (text): User’s preferred written or spoken languages
- Locale (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations
- Time Zone (text): User’s time zone
- User Type (text): User’s relationship to the organization, such as Employee or Contractor
- Employee Number (text): User’s organizatio- or company-assigned unique identifier
- Cost Center (text): Name of a cost center assigned with the user
- Organization (text): Name of the user’s organization
- Division (text): Name of the user’s division
- Department (text): Name of user’s department
- ManagerId (text): ID of the user’s manager
- Manager (text): Display name of the user’s manager
- NA (dropdown): Choose from the options available.
- Custom Search Criteria (text): Any custom search criteria you want to add.
- Sort
  
  Sort by (dropdown): Choose from the options available.
  
  Sort Order (dropdown): Choose from ASC or DESC.
Output

Result
- Users (list)
  
  Raw Output (object): Raw output returned by the Okta API.
  
  ID (text): Unique identifier of the user.
  
  Status (text): Current status of the user.
  
  Created (text): Timestamp when the user was created.
  
  Activated (text): Timestamp when the user was activated.
  
  Status Changed (text): Timestamp when the user’s status was changed.
  
  Last Login (text): Timestamp when the user last logged in.
  
  Last Updated (text): Timestamp when the user was last updated.
  
  Password Changed (text): Timestamp when the user’s password was changed.
  
  First Name (text): User’s first name.
  
  Last Name (text): User’s last name or family name.
  
  Mobile Phone (text): User’s mobile phone number.
  
  Second Email (text): User’s secondary email.
  
  Login (text): Login username of the user (usually in the form of an email address).
  
  Email (text): User’s primary email address.
Remove User from Group
Remove an Okta user from a group.

Unless otherwise indicated, field types are text.

Input
- Group
  
  ID: ID of the Okta group
- User
  
  ID: ID of the Okta user
Output
- Result
  
  Status (number): status code returned by the API:
  
  204: Successful removal
  
  404: Invalid ID–either the ID is incorrect or that user has already been removed
Remove User from an App
Remove a user from an app.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app from which you want to remove the user. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Input

Application
- App ID (text): Unique identifier of the app. This field only appears if you select Enter Application ID in the Options section.
User
- User ID (text): Unique identification of the user.
- Send Email? (true/false): If true, a removal email is sent to the admin.
Output

Result
- Status (number): Status returned by the Okta API. Here is a list of all status codes.
Update App Credentials for an Assigned User
Update an app-user’s credentials.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app from which you want to remove the user. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Input

Application
- App ID (text): Unique identifier of the app. This field only appears if you select Enter Application ID in the Options section.
User
- User ID (text): Unique identification of the user.
Credentials
- Username (text): Username of the user.
- Password (text): Password of the user.
Output

Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
System Properties
- User ID (text): Unique identifier of the user.
- External ID (text): External identifier of the user.
- Created (text): Timestamp when the user was created.
- Last Updated (text): Timestamp when the user was last updated.
- Scope (text): Scope of the user.
- Status (text): Current status of the Okta user.
- Status Changed (text): Timestamp when the user’s status was changed.
- Password Changed (text): Timestamp when the user’s password was last changed.
- Sync State (text): Sync state of the user.
- Last Sync (text): Timestamp when the user was last synced.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.
Update App Profile for an Assigned User
Update an app-user’s profile.

Required fields are indicated in red.

The input and output fields in this card are dynamically generated based on your instance.

Options
- Application (dropdown): Choose an app from which you want to remove the user. Choose Enter Application ID to select an app by its ID.
Note: The dropdown only displays 1000 apps and 2000 app instances.

Input

Application
- App ID (text): Unique identifier of the app. This field only appears if you select Enter Application ID in the Options section.
User
- User ID (text): Unique identification of the user.
Credentials
- Username (text): Username of the user.
- Password (text): Password of the user.
Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
Output

Profile Properties
- Formatted (text):
- Name (text): User’s full name.
- Nickname (text): User’s nickname.
- Given Name (text): User’s first name.
- Middle Name (text): User’s middle name.
- Family Name (text): User’s last name or family name.
- Email (text): User’s primary email.
- Profile Url (text): URL of the user’s online profile or a web page.
- Picture Url (text): URL of the user’s online picture.
- Website (text): URL of the user’s website.
- Gender (text): User’s gender.
- Birthdate (text): User’s birthdate.
- Time Zone (text): User’s time zone.
- Locale Name (text): User’s default location for purposes of localizing items like currency, date/time format, and numerical representations.
- Phone Number (text): User’s primary phone number.
- Street Address (text): Full street address component of user’s address.
- Locality (text): Locality component of the user’s address.
- Region (text): Region component of the user’s address.
- Postal Code (text): Zip code or postal code component of user’s address.
- Country (text): Country component of the user’s address.
System Properties
- User ID (text): Unique identifier of the user.
- External ID (text): External identifier of the user.
- Created (text): Timestamp when the user was created.
- Last Updated (text): Timestamp when the user was last updated.
- Scope (text): Scope of the user.
- Status (text): Current status of the user.
- Status Changed (text): Timestamp when the user’s status was changed.
- Password Changed (text): Timestamp when the user’s password was last changed.
- Sync State (text): Sync state of the user.
- Last Sync (text): Timestamp when the user was last synced.
- Credentials
  
  Username (text): Username of the user.
  
  Password (text): Password of the user.

Overview

Events

Actions

Overview

Authorizing an Account

Authorize an account from the current Okta org

Authorize an account from another Okta org

1. Create an OpenID Connect web app in the target Okta org

2. Configure the OpenID Connect web app

3. Authorize an account from the target Okta org

Events

Output

Options

Output

Output

Output

Output

Output

Options

Output

Output

Output

Output

Output

Options

Output

Output

Context

Actions

Options

Input

Output

Options

Input

Output

Input

Output

Input

Output

Input

Output

Options

Input

Output

Options

Input

Output

Options

Input

Output

Input

Output

Options

Input

Output

Options

Input

Output

Input

Output

Options

Input

Output

Options

Input

Output

Input

Output

Input

Output

Options

Output

Options

Input

Output

Options

Input

Output

Input