Personalized bulk email from your own Gmail. Upload a CSV, write one email with merge tags, and every recipient gets their own tailored copy.
App bulk-gmail.vercel.app
Sign in One-click Google OAuth — any Gmail works (personal or Workspace)
Daily cap 500 free / 2000 Workspace
SendTest, schedule, or send now — with open tracking + unsubscribe footer
Sign in, see your dashboard, connect Gmails
Any Gmail works — personal @gmail.com or Google Workspace.
Open bulk-gmail.vercel.app and click Continue with Google. The same click creates your account AND grants permission to send from your Gmail. Zero setup.
Google flags Mailroom as “unverified” on first sign-in. It’s safe — here’s why, and what to click.
Only you see your Gmails and projects.
You land on a dashboard that’s scoped entirely to you. Every user has their own — nobody sees anyone else’s Gmails, projects, or recipients. Isolation is enforced at the database level.
One project = one email send
One campaign = one project.
Name it something you’ll recognize later (e.g. Summit follow-up, Q2 prospects, May newsletter).
Any spreadsheet saved as .csv works.
Export from Excel / Google Sheets / Numbers using File → Save As → .csv.
emailfirst_name → {{first_name}}{{email}} {{first_name}} {{company}}Drag + drop or click to select.
Mailroom parses the CSV in your browser — your recipient list never leaves your device until you click Send.
Drop merge tags wherever you want personalization.
Write like a normal email. Anywhere you want the recipient’s data, type {{column_name}}. When we send, each person gets their own version — Sara sees “Hi Sara” and “Acme Group”, Tom sees “Hi Tom” and “Northbay”.
{{tag}} matching a CSV columnStop rewriting your “Hi {{first_name}}” opener.
Save any subject + body as a named template. Next time you start a project, click Insert template and pick one to drop straight into the compose fields.
Subject: Quick intro — Sara
Hi Sara, Saw what Acme Group is doing in the space — impressive. Got 15 mins this week? Best, You
See exactly what each person will get.
Use ← → to flip through every recipient. Catch typos or weird merges (e.g. a missing first_name) before a single email goes out.
Subject: [TEST] Quick intro — Sara
Hi Sara, Saw what Acme Group is doing in the space — impressive. Got 15 mins this week? Best, You — Sent from you@company.com. Unsubscribe.
✓ Test sent to you@company.com
Catch the typo before 1,000 inboxes do.
Click Send test to me. Mailroom uses the first row in your CSV as the merge sample, prepends [TEST]to the subject, and sends one copy to your own Gmail. Reply, forward, or just stare at it — whatever you’d do with the real thing.
Daily cap: 2000 · Used today: 12 · Remaining: 1988
Ready to send 4 personalized emails.
3 sent · 0 failed
Live progress, per-recipient status.
Click Send. A progress bar fills as each email flies out. Emails go out from your Gmail — recipients see your name and your email, not Mailroom. Replies come back to your normal inbox.
Scheduled to send at Tue, 9:00 AM.
Queue a send for the time your audience is awake.
Pick a date and time, click Schedule send. The project flips to Scheduledand shows up in the dashboard’s Scheduled tab. A cron job runs every five minutes; the moment your scheduled time passes, it locks the project and runs the same send pipeline (suppression list, tracking, footer included).
scheduled until it firesA tiny pixel tells you who opened.
Every HTML send includes a 1×1 transparent tracking pixel signed with an HMAC. When a recipient’s mail client loads images, Mailroom records the first open and counts every subsequent one.
opened_at on the recipient rowopen_countHi Sara, ...
Sent from you@company.com. Unsubscribe.
Click → permanent suppression. Future projects skip this email automatically.
One-click out, and they stay out forever.
Every send (real and test) carries a one-click unsubscribe footer in plain text and HTML. The link is HMAC-signed so it can’t be guessed or forged. When a recipient clicks it, Mailroom adds them to your private suppression list, and every future send across any project skips them automatically.
skipped in the project resultsLimits, privacy, and FAQ
These are Google’s rules, not ours.
Up to 500 emails per 24 hours. Mailroom defaults to this cap.
Up to 2,000 per 24 hours. Auto-detected when you connect a Workspace Gmail.
We refuse the send upfront and tell you how many slots are left. Split the CSV and resume tomorrow.
Each user’s data is firewalled from everyone else’s.
PostgreSQL row-level security enforces that queries only ever return your rows.
Your Gmail refresh tokens are stored in a column your client can never read — only the server sending on your behalf can.
No third-party sending domain. Recipients reply to you directly. No SPF/DMARC hit.
Your CSV stays in your browser until you click Send. Nothing is indexed or resold.
Quick answers.
Anyone with a Gmail. Personal @gmail.com or Google Workspace — both work. Sign-in is one click; first-timers see Google’s “unverified app” warning once and click Advanced → Continue.
Yes. Click + Add Gmail on the dashboard. Each project picks which Gmail to send from.
No. Each email is sent individually — no BCC, no blast. To the recipient it looks identical to a direct email.
The tag renders as blank in that email. Preview flags rows with missing data before you send.
Yes. Pick a date + time below the Send button. A cron job picks it up within five minutes of the scheduled moment.
Treat it as a signal, not gospel. Apple Mail Privacy Protection and Gmail’s image proxy can fire the pixel without a human seeing the email. Plaintext clients won’t fire it at all.
Per-project, yes — toggle unsubscribe_footer. We’d strongly recommend leaving it on; it’s table-stakes for deliverability and CAN-SPAM/GDPR compliance.
The dashboard and guide do. CSV upload + compose is best on desktop.
Tell the admin — accounts and all their data can be wiped from Supabase on request.