---
title: "Test sign-up, verification and reset emails in FlutterFlow apps · Proxy Mail QA"
description: "FlutterFlow apps sign in with Firebase or Supabase. Test the verification, magic link and password reset emails, including links that should open the app."
url: https://proxymail.qa/built-with/flutterflow
---

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

# Testing sign-up and verification emails in FlutterFlow apps

FlutterFlow apps use Firebase or Supabase for accounts, so those services send the emails. On a phone, the link in each one also has to open your app, which is where most problems are.

Updated 13 November 2026

## Connect FlutterFlow to Proxy Mail QA

FlutterFlow’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.

For the web version of your app: 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.

For the app on a phone or simulator, the [mobile guides](https://proxymail.qa/docs/mobile) and the [Flutter helper](https://proxymail.qa/docs/flutter) make a test address in your test, wait for the email and give you the code or link to open in the app.

## Set where links lead

- **Firebase.** Add your app’s web address under **Authentication → Settings → Authorized domains** in the Firebase console, or the links it sends are refused.
- **Supabase.** Set **Site URL** and add every address links may lead to, including your app’s deep link, under **Authentication → URL Configuration**.

## Sender and custom email

Firebase and Supabase both send from their own address until you set yours. Supabase’s built-in sender only sends a few emails an hour, so a round of test sign-ups soon runs into it; add your own SMTP server under **Authentication → Emails** before testing much. [Sign-in email limits](https://proxymail.qa/solve/auth-email-limits) covers each service.

## 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 under **Authentication → Users** in Firebase or Supabase.

## 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=flutterflow)

## Questions

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

Not today. FlutterFlow lets other AI tools work on your project, but its own AI doesn't connect to other tools. Test from Chrome on the web version of your app, or with the mobile helpers on a phone.

### Why does the link open the browser instead of my app?

The link has to point to an address your app is set up to open. Check your app's deep link settings in FlutterFlow and the redirect address your sign-in service allows; the mobile guides show how to follow the link from a test.

## 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.
- [WeWeb](https://proxymail.qa/built-with/weweb): Test the sign-up and reset emails your WeWeb app's sign-in service sends, from Chrome.
- [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)

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