Hi Ethan, Thanks for awesome work.
But for my case, this workaround return a list of emails for me instead of identifying username’s email in database.
Any clue?
Hi Ethan, Thanks for awesome work.
But for my case, this workaround return a list of emails for me instead of identifying username’s email in database.
Any clue?
I haven’t tested this but I believe we can create two workflows behind the “sign in” button. The first button workflow would only trigger if the input “email/username” contains “search for user:usernames”, the second button workflow would only trigger if input “email/username” contains “search for user:email”.
Pretty straight forward, I believe this would for newer platforms. Platforms with thousands of users might be a bit slower as you’re performing a search across the entire user database.
Cheers
Nice approach but too expensive with the new WU system. Have you change your above example @jackbrandt788 ?