Email campaign automation that runs inside your own Gmail account: schedule the send, queue the next campaign, let pacing and daily limits handle the throttle, and have opt-outs suppressed without you touching a spreadsheet. By SoftCofee.
Six moving parts, no servers reading your recipient list
Set a date and time and the campaign waits for its slot instead of firing now. Monday-morning outreach stops being a manual task you have to be awake for.
Line up a batch of campaigns. They run one at a time, so batches never fight each other for the same daily quota or trip Gmail's rate limits.
If your list is bigger than your daily limit, DraftMerge works out how many days it needs and sends in numbered parts, resuming where it stopped.
A randomized pause between messages, configurable, so a campaign looks like a person writing email rather than a burst of identical sends.
Unsubscribes land in your workspace sheet and feed a local suppression list that is checked before every single send. Opted-out addresses are skipped, not mailed again.
Tick the cleanup option before you send and the messages a campaign put in your Gmail are removed when it finishes, so a 4,000-recipient run does not bury your mailbox.
Import an Excel or CSV file, or point DraftMerge at a Google Sheet. Each row becomes a recipient, and each column becomes a merge token you can drop into the template.
Add {{First Name}} style tokens, a subject line, and your footer. Personalization is what separates a mail merge from a blast.
Render sample rows locally to check tokens resolved, then send yourself one test message. Nothing is queued or scheduled until you say so.
Hit Start Campaign, or pick a later date and time and let the timer launch it. Keep Chrome open while a campaign is running - sending happens on your machine, which is also why your recipient list never travels to us.
Sending business emails through Gmail this way keeps your domain reputation intact: messages go out from your own account, at human speed, to people who have not asked to stop.
There is no cloud scheduler. A campaign sends while your browser is running, which is the direct trade-off for recipient data never leaving your machine.
Queued campaigns run sequentially on purpose: parallel campaigns on one mailbox simply compete for the same daily limit.
Automated follow-up sequences with per-stage delays are not shipped. Today you schedule each touch as its own campaign. If sequences matter to your workflow, tell support - it is a roadmap candidate.
DraftMerge cannot raise what your account may send. It plans around the limit you have. See the deliverability guide for staying inside it well.
Yes. Pick a date and time next to Start Campaign and the campaign is stored as scheduled instead of running immediately. A background timer activates it when the time arrives. Chrome has to be open at that moment, because sending runs on your machine rather than on a server.
DraftMerge splits it automatically. It calculates how many days the list needs, pauses when the daily limit is reached, and resumes the next day on the remaining rows, showing a Day X of Y progress badge while it works through the parts.
Not yet. A campaign sends one message per recipient. For a follow-up today, run a second scheduled campaign filtered to the people who should receive touch two. Multi-step sequences with per-stage delays are not available; tell support if you need them, because customer demand shapes what we build next.
Yes. Every message carries a List-Unsubscribe header and your footer link, opt-outs are written to your workspace sheet, and the suppression list is checked before each send so matching recipients are skipped rather than mailed.
Free forever for up to 50 emails a day. Three-day Premium trial with no credit card.