The custom field is from the Jira  service management form

Hi @User15717589852053945299 (Customer)​,

Thank you for posting on the Okta community page!

Based on the screenshots provided it seems that the wrong data is being pulled when using the email attribute on the Flow Control Assign card because the value returned is mnl okta1 instead of mnlokta1@remitly.com.

If the value would be an email instead of the user name, I assume that you would not receive the 404 error and that the flow would work, therefore I would recommend to check if there are any fields on the Jira side that you could use to pull the email value.

------------------------------------------------------------------------------------------------------------------------------------------------

The Okta Community November newsletter is here. Get product updates and see our top contributing members.

Hi @flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)​ ,

We've made some changes to the workflow. We added "List Users with Search" so that we can capture the email address. But still, an error was received. You can check the image below for your reference.



@User15717589852053945299 (Customer)​ 

The issue is you are passing an invalid value into the read user. Read user input requires an Okta UID value OR the login value (which is typically an email address).

Since I cannot see the full payload you are receiving on the API endpoint I cannot determine if "Email address" is a value contained in the payload. Keep in mind this received payload is a "RAW" send from the provider (JIRA) and the content of this data has nothing to do with Workflows. Workflows can only work with what is received.

The "List users with X" is likely not going to work. displayName is not a populated attribute by default and even if it is populated it is not a unique attribute. You could potentially have 50 Raymond Cruz in your org. How are you going to determine which is the correct one for the input you want to take action against?

Ultimately, you need to capture a usable value (often Email) that can be passed down stream into read user card if you have specific attributes you want to pull information from due to the requirements of unique values (Okta ID / Login) being required for read user.