---
title: "Test sign-up and login emails in WeWeb apps · Proxy Mail QA"
description: "WeWeb apps sign in through Supabase, Xano or Auth0, which send the emails. Test them with private inboxes from Proxy Mail QA for Chrome."
url: https://proxymail.qa/built-with/weweb
---

1. [Home](https://proxymail.qa/)
2. [AI app builders](https://proxymail.qa/built-with)

# Testing sign-up and login emails in WeWeb apps

WeWeb builds your app's front end and leaves accounts to a sign-in service such as Supabase, Xano or Auth0\. That service sends the emails and decides where their links lead.

Updated 13 November 2026

## 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](https://proxymail.qa/chrome-extension) 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**.

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=weweb)

## Questions

### Can WeWeb's AI use Proxy Mail QA?

Not today. WeWeb's AI works inside the editor and doesn't connect to other tools. Test from Chrome instead.

### Where do I set where the email links lead?

In your sign-in service, not in WeWeb: in Supabase, Authentication → URL Configuration; in Auth0, the application's allowed callback addresses.

## Related guides

- [Lovable](https://proxymail.qa/built-with/lovable): Which Lovable Cloud logins send email, the Site URL and sender settings, and a check before you launch.
- [Replit](https://proxymail.qa/built-with/replit): Replit Auth, Clerk Auth or your own: which send email, and how to test each on the published app.
- [Bolt](https://proxymail.qa/built-with/bolt): Turn on email confirmation, fix the localhost Site URL and test every auth email before you publish.
- [Base44](https://proxymail.qa/built-with/base44): Test the sign-up code, password reset and invites, and every user role, with a test account per role.
- [v0](https://proxymail.qa/built-with/v0): Set Supabase’s Site URL and redirects for Vercel deployments, or move Clerk to production, then test every login email.
- [Bubble](https://proxymail.qa/built-with/bubble): Test sign-up and password reset emails in your Bubble app from Chrome, and clear the test users out afterwards.
- [FlutterFlow](https://proxymail.qa/built-with/flutterflow): Test Firebase or Supabase sign-in emails in your FlutterFlow app, including links that should open the app on a phone.
- [Softr](https://proxymail.qa/built-with/softr): Test your Softr app's sign-up, magic link and password reset emails from Chrome, and clear the test users out afterwards.
- [Glide](https://proxymail.qa/built-with/glide): Test the PIN email your Glide app sends to sign people in, from Chrome, and clear the test users out afterwards.
- [Claude Code](https://proxymail.qa/built-with/claude-code): Check the auth emails in apps you build with Anthropic’s coding agent, from localhost to staging.
- [OpenAI Codex](https://proxymail.qa/built-with/codex): Run the real email flow once before you merge a Codex change that touches sign-up or login.
- [Qoder](https://proxymail.qa/built-with/qoder): Check the real sign-up, code and reset emails after the agent changes your auth code, or let it check them itself.
- [Cursor](https://proxymail.qa/built-with/cursor): Check the real sign-up, magic-link and reset emails after the agent changes your auth code.
- [Google Antigravity](https://proxymail.qa/built-with/antigravity): Keep unverified Firebase users out, check authorized domains and the sender, and let the agent run the check.
- [Login methods explained](https://proxymail.qa/built-with/login-methods): Email, codes, magic links, Google and Apple buttons, phone and SSO: what each sends, what breaks and how to test it.

[See every email testing problem we solve](https://proxymail.qa/solve)

WeWeb is a trademark of its owner. Proxy Mail QA is independent and isn’t affiliated with or endorsed by them.
