How to Send Bulk Emails from a Spreadsheet Without Zapier or Make

You have a spreadsheet. It has 200 rows. Each row is a customer, and each customer needs an email that mentions their specific invoice number, amount due, and due date.

You Google "how to send bulk emails from Excel." You find an article about Zapier. You open Zapier. You read about task limits and pricing tiers. You close Zapier.

You Google "mail merge Gmail." You find a 14-step tutorial involving Google Sheets, a Gmail add-on, and a template document. Step 9 doesn't work. You close that too.

Here's the thing: sending personalised emails from a spreadsheet should not require a 45-minute setup process. Here's how to do it in under 5 minutes.

Why Zapier and Make aren't built for this

Zapier and Make are excellent tools for connecting apps — "when X happens in tool A, do Y in tool B." That's what they're designed for.

But "take 200 rows from a CSV and send a personalised email for each one" isn't really an app-connection problem. It's a data processing problem. Zapier charges per task, which means 200 emails costs 200 tasks. Make has row limits. Both require you to maintain a Zap or scenario that breaks every time your column names change.

For a one-click, bulk send from a spreadsheet, there's a simpler path.

What you actually need

Three things:

• A CSV or Excel file with an email column (and whatever other data you want to use in the message)
• A Gmail account to send from (or any SMTP server)
• HEVFY — free during beta

Setting it up (once, takes 3 minutes)

Go to HEVFY → Integrations → Gmail and click Connect. You'll go through Google's standard OAuth flow — the same one you use to connect any Google app. HEVFY requests permission to send emails on your behalf. No passwords, no SMTP settings, just OAuth.

That's it. You're connected. You never have to do this again.

Sending your first batch

Upload your spreadsheet. Your columns become variables you can reference. A typical invoice reminder file:

email,customer_name,invoice_no,amount,due_date,days_overdue
priya@startup.io,Priya Kumar,INV-0041,₹24500,March 15 2026,12
james@agency.co,James Wilson,INV-0042,₹8200,March 10 2026,17

Now describe the email in plain English:

"Send each customer a payment reminder. Use their first name in the greeting. Mention the invoice number and amount due. Include the due date. Keep the tone professional but warm — not threatening. For anyone more than 14 days overdue, add a line about contacting us to discuss payment options."

HEVFY writes a personalised draft for each row and shows you the first few before sending anything. Priya's email looks different from James's — different overdue period, different invoice details, slightly different tone because she's under 14 days and he's over.

You read them. They're good. You click send.

Both emails go out in seconds. If you had 200 rows, they'd all go out in about a minute.

The whole process from file to sent emails:

The deliverability advantage most people don't think about

When you send from your own Gmail account, the email comes from a real address with an established sending history. Google knows your account. Recipients recognise your domain. The emails land in inboxes.

Contrast that with bulk email services — Mailchimp, Brevo, SendGrid — which route your emails through shared IP addresses used by thousands of other senders. If any of those senders have bad reputations, your deliverability suffers too.

For transactional, personalised emails to your own customers, sending from your own Gmail is usually better for deliverability than a bulk email platform. Especially for the volumes most small and mid-size teams are working with (under 500 per day).

Save it — so next month takes 10 seconds, not 5 minutes

Once you've set this up and it works, HEVFY saves it as an automation. Give it a name: "Monthly invoice reminders."

Next month, upload the new CSV, click run. The same personalised emails go out, with the new data, in under a minute. The logic is saved. The Gmail connection persists. There's nothing to rebuild.

Three months from now, you'll have completely forgotten that this used to take half an afternoon.

What else teams do with this

Once the first email automation is running, teams usually find three or four more uses almost immediately:

• HR teams sending individual salary slips to each employee (each gets their own numbers, not a shared report)
• Sales teams sending personalised follow-ups after events, referencing the specific conversation or product discussed
• Ops teams sending weekly status updates to clients, each one referencing that client's specific project data
• Finance teams sending monthly statements where each email contains only that customer's transactions

The common thread: any task where you have a list of people and each one needs a slightly different message. That's the automation. The data is already in your spreadsheet. You just need a way to use it.