Hello @TonyT.19130 (Customer)​ - I am assuming you are using an Okta Event card (Likely "user created") to start the invocation of the flow (Cause it to execute).

How this works is when a Flow with an Okta Event card is started it makes a call to Okta Core to first setup an Event Hook to monitor for a specific eligible event. Okta then monitors for when that event occurs then delivers a payload of data to a destination (In this instance the Okta Workflows Event card which is also an API endpoint)

For you to make a differentiation there would need to be some sort of data you can evaluate against to so you can make a logical choice. So for example: Continue if the value meets something that uniquely identifies Bamboo as the source otherwise stop the flow. What I don't know is if the event data you are using to trigger the flow start contains this data (I don't have Bamboo HR so I can't test it).

You would want to leverage Flow History and compare a Bamboo "user create" event against other "user create" events and see if any piece of data allows you to 100% guarantee it originated from BambooHR. If that exists then you can just pull that piece of data (Using something like an Object Get) that can be passed into the continue if for evaluation.

Object - Get allows dot (.) pathing to the specific item in the JSON. So for example:

{

 "key2": "value2",

 "key1": {

  "newkey1": "newValue1",

  "newkey2": "newValue2"

 }

}

If I wanted the value for newkey1 the path would be: key1.newkey1

Which would return newValue1

I mentioned this because the identifying data, if it exists, would be nested pretty deep in the JSON.