In terms of using Okta Workflows, you won’t be able to redirect the user’s browser or really have control of where they wind up.
Your suggestion about Routing Rules seems like it might come into play, but I’m not entirely sure… it might be worth reaching out to your account team to see if they have more information about something like this integration: https://www.okta.com/sites/default/files/pdf/okta_experian-datasheet.pdf
In terms of using Workflows, you could do things like what’s mentioned here: Perform identity proofing with a third-party service | Okta
You’d probably be looking at more of an async process that’s not in line with a user’s authentication… as an example:
- User self registers for your Org
- Kicks off a flow that does something like EvidentID - Create Transfer Request and tracks the request ID in a table or on the user profile.
- When request completed, update that user… mark an attribute that is linked to group rules or do something that gives them access to their stuff.
Workflows would probably work best in that kind of async framework outside the authentication pipeline.
Otherwise, someone else might have more information about some of this: Identity Proofing - Okta Integration Network | Okta - never hurts to ask your account team.