<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009xPe16CACOkta Identity EngineWorkflowsAnswered2024-03-08T00:44:18.000Z2024-01-15T14:02:49.000Z2024-01-16T22:57:15.000Z
  • TimL.58332 (Workflows)

    @SteveF.61090 (Customer)​ - Going to expand on Daniel's answer a bit.

     

    In Okta there are 2 categories of Sys Log events. "Event Hook Eligible" and those that are not. "Event Hook Eligible" events can be monitored in real time and have a payload be delivered to a designated location (Such as Workflows API Endpoint).

     

    For the Events that are not possible what Daniel described is the method available

     

    For detailed information about events (And instructions on how to see which ones are eligible) see the following article:

     

    https://developer.okta.com/docs/concepts/event-hooks/

     

    One other mention: Okta Workflows has a bunch of built-in Event cards for a good number of events. However, these are going to be 1-to-1 flow to event. If you have multiple events you want to feed a single flow you will want to leverage Okta Core's event hooks directly under Workflow > Event Hooks. This allows for you to monitor multiple different eventTypes in a single hook with a single destination.

    Expand Post
This question is closed.
Loading
Use Okta Workflows to Trigger Jira Issue Creation