---
title: "Test sign-in PIN emails in Glide apps · Proxy Mail QA"
description: "Glide apps sign people in with a PIN sent by email. Test it with private inboxes from Proxy Mail QA for Chrome, then clear the test users out."
url: https://proxymail.qa/built-with/glide
---

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

# Testing sign-in PIN emails in Glide apps

Glide apps sign people in with a PIN sent to their email. If it's slow or lands in spam, nobody gets in, so it's the first email to check.

Updated 13 November 2026

## Connect Glide to Proxy Mail QA

Glide 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.

You can also make an address in the Proxy Mail QA app, type it into your app’s sign-in screen and copy the PIN from the email’s row.

## What to test in a Glide app

- **The PIN email.** It should arrive within seconds; check it does, and that asking for a new one works.
- **Who can sign in.** If your app only lets in people on a list, sign in with one address on it and one that isn’t.
- **Emails your app sends,** such as notifications from workflows.

## 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 their rows from your app’s users table in the Data Editor.

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

## Questions

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

Not today. Glide doesn't connect its AI to other tools. Test from Chrome, or by hand, instead.

### Who sends the PIN email?

Glide, from no-reply@auth.appnotify.io. Proxy Mail QA shows the PIN with a Copy button as soon as it arrives.

## 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.
- [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.
- [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)

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