I know we can setup provisioning in a SCIM enabled app to automatically create new Okta accounts under certain conditions, but we in IT like to doublecheck the data coming over from the other platform before letting it into our Okta environment.
Right now we just go to the app in Okta, check the provisioning tab, check the data under the app assignment, and then manually push the account through activation. Instead I would like to explore if there is a way we can perform that action remotely.
I can get the data from the other app and pipe that into our Jira ticket for review easily enough. Assuming all the data checks out, I would like to run a Jira action that would “approve” the user and create their new Okta account from the SCIM provisioning supplied in that app just like the manual process.
Is there any endpoint or means of doing that via Workflows?
Hi @Dee_Queue,
So, the short answer is that if there is an API, you can build a flow to call it in Workflows.
This blog post talks more about what you can do with Workflows: Can I do this with Okta Workflows?
I would like to run a Jira action that would “approve” the user
Since it seems “approve” is a custom logic, you can read the Jira ticket, verify that it has all the required information in a flow, and create a new user in Okta (using the Okta Create User action).
Alternatively, if you are certain the information in a Jira ticket is correct, you can skip the verification step and proceed to creating a user.
Let me know if this helps.
1 Like
So… to be completely honest, that wasn’t the idea I had in mind. BUT… You helped me to break out of the single track mindset I had going into this effort. 
I can just pull all the new user details from the other platform, check/edit the data in our Jira ticket, and then send the data back to Okta and have it perform the create user action like you outlined. Thank you!
The extra details nobody asked for
It’s so simple now that you helped to reframe my view.
I was locked into the mindset of having to utilize the scuffed SCIM enabled application we had setup for Paylocity in our Okta.
Last year we bit the bullet and paid for API access beyond the limited SCIM fields to help with various actions and automations we wanted to enact… We also had two different apps setup in Okta. One setup to allow SSO login and the other for the SCIM provisioning… I, should, be able to now get rid of the scuffed SCIM enabled app and just lean on the full API.
That’s awesome, I’m glad it helped.