MergeFlow sends personalized email from a Google Sheet through your own Gmail — with one privacy promise most mail-merge tools can't make: it uses the send-only Gmail permission, so it physically cannot read, search, or open your email.
When a Google permission screen asks to "read, compose, and modify your email," that's the tool asking for your whole inbox. MergeFlow never asks, because it doesn't need it.
gmail.send onlyBuilt for freelancers, founders, recruiters, and outreach teams who have outgrown BCC.
Not everyone should get the same email. {{#if role == "CEO"}} founder pitch {{else}} team pitch {{/if}} — personalization beyond first names.
Optional pixel and wrapped links, served by a Cloudflare Worker you control. No third-party analytics, no data broker, opt-in per campaign.
Send status, opens, and clicks land in columns of your Google Sheet. The sheet stays the source of truth.
Sends at a pace Gmail trusts, with sensible defaults you can tune. Your deliverability is the whole point.
Queue automatic follow-ups after N days. Mark a row replied and its follow-ups stop.
Your contacts and messages go straight from your browser to Google's APIs. No middleman server stores your data.
Four steps from sheet to sent.
Pick the Google Sheet with your recipients and fields.
Merge fields and conditional blocks, straight from your column names.
See each personalized message resolved before anything sends.
Paced sending, live progress, results written back to the sheet.
Start free. Upgrade when your volume does.
Really. The extension requests only gmail.send, spreadsheets, and userinfo.email. Google enforces scopes at the API level — a send-only token cannot list, search, or open messages. It's not a policy promise, it's a technical boundary.
In your browser and your Google account. Settings, campaign history, and send counts live in Chrome extension storage on your device. Your sheet and emails go directly between your browser and Google's APIs.
Manually, by design. Mark a row replied (the MF_Replied column) and its follow-ups stop. Automatic reply detection would require a Gmail read scope — that's the exact permission we refuse to ask for.
MergeFlow paces sends to stay well inside Gmail's comfort zone, and you stay inside Gmail's normal sending limits for your account type. You remain responsible for emailing people who want to hear from you — see the terms.
It's in Chrome Web Store review preparation now. Email us and you'll get one message when it's live — nothing else.