Hi! Great question and thanks for reaching out. I have the same setup (Workday >> Okta).

Please take a look at how I have implemented this and please do let me know if you have any questions and if this will/wont work for you! Thanks again.

The trigger is "User Okta Profile Updated", then we will look specifically for the attribute we care about "Find", then determine if it changed "Continue If". If it changed in my own flow, I proceed with the rest of the automation and stop it if it did not change. Let me know what you think!

Hi Don! Thanks for reaching out and taking a look at my question!

We have a couple different attributes we'd like to trigger the flow, but no matter what attributes I change, it doesn't even trigger the flow at all. I'd like to analyze the Flow History tab, but there are no recent executions. Do I need to have that `find` card in to make it work?

What attributes do you change on your user's profile to trigger the flow? Or does it trigger no matter which attributes are changed (Workday controlled, manual attributes etc.)

Best,

Kaeley

Hi Kaeley. As a test, create a second workflow ( disable the current one ) and do a basic test of an Okta profile update to see if it triggers with just a Compose card or something similar. Certainly it should do what it says on the tin and trigger the flow if you have updated the Okta profile, regardless of the source of that profile update.

Also, just make sure the Workflow is actually enabled as well ;)

Hello Kaeley,

Lets get into the weeds a bit.

The Okta - Event cards such as "Okta User Profile Updated" is made up of two parts:

1) An API call to Okta core to create/delete an Event Hook for an event-hook-eligible event (user.account.update_profile in this instance)

2) An API Endpoint to receive a payload from the Event Hooks which will invoke a flow start.

So when a flow that contains one of these Event cards is started the API call will occur to setup the Event hook. When the flow is stopped an API call will occur to remove the Event hook

What then occurs is Okta Core then monitors for that specific event to occur. This will show up in your System Log. In the System Log "IF" an Event Hook is monitoring the specific event the DebugData will have an additional property called "TargetEventHookIds" which will contain a GUID for the Event Hook. If this is not present in the System Log event the Hook is either not setup or it exceeded the maximum daily deliveries.

So in your instance you would want to do the following:

1) Confirm your flow is started (You may want to Stop, then Start it). Wait a good 15-20 seconds.

2) Modify a user profile attribute (The source of the modification won't matter you can just do this manually)

3) Search the System Log for: user.account.update_profile

4) Expand the found event for that test user and look for TargetEventHookIds in Debug section

If this is not found then I would open a support case. If it is found then the payload was likely delivered.

Second part (post getting the event payloads):

You mentioned "multiple attributes you wanted to track". Don's example is looking for just one. In a scenario where you have multiple you want to track the complexity goes up quite a bit. You will want to do a series of compares similar to how Don leveraged the Continue If. You can then determine if any of those compares are True. If you have different actions you want to take based on the found attribute you can then use the previous compares T/F in an If/Else series and if the compare was True perform the logic, and if False don't.

I tried doing that and it does work! But for some reason despite having the same trigger, one flow runs successfully and the other doesn't--like it doesn't even begin/show logs/errors

So in a scenario where have 2 event hook targets for the same event the TargetEventHookIds should list out 2 unique event hook ID's in the System log events (It is impossible to tie them to a specific flow from the System Log so just rely on count matching what is expected)

I would try the following:

1. Turn the flow off
2. Remove the Event card
3. Save the flow
4. Add the event card
5. Save the flow
6. Turn the flow back on
7. Test

 If that doesn't work you may just want to rebuild the flow (Create a new flow, recreate the cards.. don't do a duplicate as the problem that might be in the existing flow would just duplicate)