Sync User in External Application

Trigger a Flow when an admin syncs users from an external application to Okta.

Unless otherwise indicated, field types are text.


  • Use App Instance ID?(dropdown): Choose from Yes or No. If Yes, you can select the application instance directly through the App Instance ID field.

  • Application (dropdown): Choose the app to trigger a Flow for when an admin syncs a user. Choose Enter Application ID to select an app by its ID.

    Note: This displays a maximum of 1000 apps.

  • Application Instance (dropdown): Choose from a list of existing application instances, dependent on the application chosen in the previous step.

    Note: This displays a maximum of 2000 app instances. This event will only trigger for the selected application instance. If you don't see your application instance in the list use the Use App Instance ID? dropdown list and the App Instance ID field to be able to trigger the event for a specific application instance.

  • Application Instance ID: A unique app instance ID. Note: Choose Yes in Use App Instance ID? to interact with your application instance directly through its ID.

    To find the application instance ID for an app:

    1. Go to Okta Admin Console > Applications.

    2. Click your app. The app page opens.

    3. Check the page URL.

      You can find the app ID using this URL pattern:

      For example, Here, 0oahjhk34aUxGnWcZ0h7 is the app instance ID.


  • Date and Time: The date and time the event was triggered in Okta API.

  • Message: Message details about the event.

  • Event ID: The event's unique identifier key.

  • Event Type: The type of event that was published.

  • Event Time: The timestamp when the notification was delivered to the service.

  • Version: The versioning indicator.

  • Admin (object): The Okta admin who synced the user.

    • ID: The ID of the Okta admin who synced the user.

    • Alternate ID: The email address of the Okta admin.

    • Display Name: The display name of the Okta admin.

    • Type: The admin type.

  • Okta User (object): The Okta user who was synced.

    • ID: The user's ID.

    • Alternate ID: The user's email address.

    • Display Name: The user's display name.

    • Type: The type of Okta user.

  • Application User (object): The user's details for the target application.

    • ID: The user's ID in the target application.

    • Alternate ID: The user's alternate ID in the target application (usually their email address).

    • Display Name: The display name of the user for the target application.

    • Type: The type of user in the target application.

  • Application (object): The target application.

    • ID: The ID of the target application.

    • Alternate ID: The alternate ID of the target application.

    • Display Name: The display name of the target application.

    • Type: The type of the target application.

  • UUID: The webhook event's universal unique identifier.

  • Event Details (object): The raw JSON payload returned from the Okta API for this particular event.

  • Headers (object): The object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (Content-Type: text/plain).

  • Source (object): The source of user-specific data.
  • Debug Context
    • Debug Data: (object) The information on the triggered event used for debugging; for example, returned data can include a URI, an SMS provider, or transaction ID.

Related topics

Okta connector

About the elements of Okta Workflows

Okta API