Connect WeWeb to Proxy Mail QA
WeWeb’s AI doesn’t connect its builder AI to other tools (it lets other AI tools work on your app instead), so there’s nothing to connect Proxy Mail QA to there. Test from your browser instead.
Proxy Mail QA for Chrome fills the sign-up form with a test address and shows the code or link when the email arrives. Open your app (not the editor) in its own tab, click the extension and turn it on for that address. Proxy Mail QA for Chrome has more.
Set where links lead
Links in sign-up and reset emails go to whatever your sign-in service allows. Add your app’s preview and published addresses there: in Supabase, Site URL and the redirect list under Authentication → URL Configuration; in Auth0, the application’s allowed callback addresses. A link that leads to the wrong place usually means one of those is missing.
What to test in a WeWeb app
- Sign-up and its confirmation email, if your sign-in service sends one.
- Password reset, from request to signing in with the new password.
- Magic links or codes, if you use them.
If you use Supabase’s built-in sender, it only sends a few emails an hour; set your own SMTP server under Authentication → Emails before testing much.
Clear out test users
Every test sign-up leaves a user in your app. When you’re done, open Project settings → Test users to delete in Proxy Mail QA: it lists every test address the project used, live or gone, and the domains they end in, so you can find them all in your user list. Then delete them in your sign-in service: in Supabase, Authentication → Users.