When using the CREATE User API, if a user is created without a password, and they later attempt to sign up with the same email, the system currently returns “user already exists.”
Instead, it’d be awesome to detect that no password was set and prompt these users to create one, rather than blocking signup with an error.
On this note, want to add some context here as I think there’s some bugs as well:
Currently when you use Pickaxe | Build & Manage AI Agents
And you don’t set their password for them, if they try to log in with that email, it’ll say “invalid credentials” or something like that. Because there’s no password yet.
IF you use a Magic Link which I thought might be the solution to get them to set their password, they will try to log in and get this error: “User does not have a password, use the correct log in method:
I think the cleanest solution is if the user has no password in their user details, there’s a popup when they try to log in or sign up that asks them to set their password.
Right now we’re including our Pickaxe with another thing we’re doing and mass creating accounts for 1000+ people. The language we’re using in the meantime is coaching people to use the “forgot password” feature with the email we have on file and that’s the most reliable way to get in.
I’m also very much in favour of this solution!
@stephenbdiaz I’m curious: where are you sending them with the Forgot Password link?
@akpsolutions we do a lot of virtual events so we’re just being sure to tell people that when showing the software, this reduces our customer support tickets.
Something like, go to [DOMAIN], and when you get there we already created an account for you, but you need to set a password. So click log in, click forgot password, and then you can set your password and you’ll be good to go!
We also have this language in a welcome email that is sent to them so my zapier looks like this:
trigger (purchase or form fill out etc)
v
custom webhook using pickaxe api to create user
v
custom webhook using pickaxe api to invite user (in my experience this is not working yet)
v
CRM (our own crm) sends email welcoming new user, directing them to log in and walk through the forgot password method
Thank you for sharing this valuable feedback and the screenshots. I’ve passed this along to our team.
For now, the most reliable approach is to set passwords when creating users via the API so they can log in immediately, and update it later at their convenience or prompt them to enter a password somewhere during your workflow and include it in the API call. You can also set or update passwords anytime in the Users tab under Manage Users by opening a user’s profile. Another good option is to use the Studio API to send email invitations so users complete signup and set their own credentials through that flow.
Oooo this gave me an idea @danny_support thank you! I will have them set their password somewhere else and send that data to the API call, this will work for now (I think!) I’ll report back 
