How to Automate Email Workflows With Make.com

For most solopreneurs, email is the most expensive part of their workday — not in subscription cost, but in time. Welcome emails, intake responses, project update notifications, invoice follow-ups, deliverable confirmations, check-in messages, meeting prep reminders — the list of recurring emails that need to go out on schedule is long, and sending them manually is death by a thousand tiny tasks. Make.com automates all of it. Unlike simple email platforms that handle drip sequences, Make.com connects your email to every other tool in your stack: your CRM, your project management tool, your invoicing platform, your scheduling tool. When a client moves to a new project stage in Notion, Make sends a status email. When an invoice goes overdue in Wave, Make sends a payment reminder. When a Calendly booking is confirmed, Make sends a prep questionnaire. This guide covers the specific email workflows that save solopreneurs the most time, with step-by-step setup for each one.

Why Make.com Beats Email Platforms for Complex Email Automation

Standard email marketing platforms — Mailchimp, ConvertKit, Brevo — are built for broadcasting to lists. They handle drip sequences, open-rate tracking, and list segmentation well. What they don’t do is respond dynamically to events in your other tools. They can’t detect that a project in your Notion workspace just moved to “Deliverable Sent” and trigger a client notification. They can’t watch your invoicing tool for overdue payments and fire a reminder. They operate in isolation from the rest of your business.

Make.com operates across your entire tool stack. A scenario can watch for a trigger anywhere — a new row in Airtable, a new event in Calendly, a new payment in your billing tool, a status change in ClickUp — and send a precisely crafted email in response. The conditional logic layer is where Make genuinely outperforms simpler tools: you can route different email templates based on the data in the trigger, apply filters so only certain events fire the email, and build multi-branch scenarios where a single trigger produces different outcomes depending on field values. No code required — just the visual scenario builder.

For solopreneurs who have explored Zapier for email automation and hit the limitations of its linear workflow model, Make.com’s branch and router modules are the key differentiator. Our detailed comparison of Make.com vs Zapier for small business covers exactly when it’s worth switching — email workflows with conditional logic are one of the clearest cases.

Setting Up Make.com for Email Automation: The Basics

Before building your first email scenario, you need two things configured in Make.com:

1. Gmail connection — Make.com connects to Gmail via OAuth. Go to your Make.com account, navigate to Connections, search for Gmail, and authorize. This gives Make.com the ability to both read emails (as a trigger) and send emails (as an action) from your Gmail account.
2. Email templates stored somewhere accessible — Make.com doesn’t have a native template library. Store your email body text in a Google Doc, a Notion page, or directly in the Make.com module’s text field. For longer emails with dynamic fields (client name, project name, due date), the text editor in each Gmail module handles merge variables using Make’s double-curly-bracket syntax: {{contact.name}}, {{project.title}}, etc.

Make.com’s free plan gives you 1,000 operations per month across unlimited scenarios. For solopreneurs handling 10–20 email automation events per month, the free tier covers everything. The Core plan ($10.59/month) is worth it once you exceed the free tier or need scenario scheduling at intervals shorter than 15 minutes.

The Five Email Workflows Worth Automating First

Workflow 1: Intake Form → Instant Response + CRM Update

Trigger: New submission in Typeform, Tally.so, or Google Forms
Email sent: Immediate acknowledgment to the lead — “Got your message, here’s what happens next”
Additional actions: Create or update contact record in Airtable or Notion CRM

Make.com scenario structure:

1. Watch for new Typeform/Tally submission
2. Router module: branch based on service type field (e.g., “Web Design” vs. “Copywriting”)
3. Each branch: Send Gmail with service-specific response template, pre-filled with the lead’s name and stated project type
4. Create record in Airtable Contacts database with all form fields mapped

The router module is what makes this scenario more powerful than a simple Zapier workflow — one form submission sends different emails and creates different project types based on the lead’s selections, without building separate scenarios for each service type.

Workflow 2: Project Status Change → Client Notification Email

Trigger: Record status changes in Notion, Airtable, or ClickUp
Email sent: Proactive project update to the client (“Your project just moved to [stage] — here’s what that means and what happens next”)

Make.com scenario structure:

1. Watch Notion database for records where Status field changes (Make.com polls on a schedule)
2. Filter: only proceed if new status is one of: “In Review,” “Deliverable Sent,” “Revision Requested,” “Complete”
3. Get the linked Contact record from Notion to pull client email address and name
4. Send Gmail with status-specific template — different email body for each status value

This single scenario eliminates the manual project update emails that eat 15–20 minutes per project per week. The client feels informed without you having to remember to tell them. Our guide on automating client reports with Make.com covers the related workflow of generating and sending automated status reports — this notification scenario is a lighter-weight complement to that full reporting system.

Workflow 3: Calendly Booking → Meeting Prep Email

Trigger: New Calendly event created
Email sent: Meeting confirmation with prep questions, agenda, and anything you need the client to bring to the call

Make.com scenario structure:

1. Watch Calendly for new events (Make.com has a native Calendly module)
2. Filter: only fire for specific event types (e.g., “Discovery Call” not “Quick Check-In”)
3. Send Gmail to the invitee with meeting prep template: what to expect, what to prepare, how to reschedule
4. Create task in ClickUp or Notion: “Prep for [Name] call” due 30 minutes before the call time

The combination of the client prep email and your own prep task means both sides arrive at the call ready — without you sending anything manually. Pair this with the broader Calendly automation setup covered in our guide on using Calendly to automate client scheduling for a complete scheduling automation system.

Workflow 4: Invoice Overdue → Payment Reminder Sequence

Trigger: Scheduled — Make.com runs daily at 9am
Email sent: Payment reminder to any client with an overdue invoice

Make.com scenario structure:

1. Schedule trigger: runs daily at 9am
2. Search Airtable Finances database for records where Status = “Sent” AND Due Date is past today
3. For each overdue invoice: Get linked Contact record to pull client email
4. Calculate days overdue using Make’s date math tools
5. Router: send different email template based on days overdue (1–7 days: gentle reminder; 8–14 days: firmer notice; 15+ days: formal final notice)
6. Update Airtable record: log reminder sent date and template used

This scenario runs silently every morning, checks for overdue invoices, and sends appropriately escalating reminders without you ever thinking about it. The three-tier escalation logic — friendly, firm, final — is only possible because of Make’s router module. A simple Zapier workflow would send the same email every day regardless of how overdue the invoice is.

Workflow 5: New Client Signed → Onboarding Email Sequence

Trigger: Contact status changes to “Active Client” in your CRM (Airtable or Notion)
Email sent: Kickoff email, then Day 3 check-in, then Day 7 feedback request

Make.com scenario structure:

1. Watch CRM for status change to “Active Client”
2. Send kickoff email immediately with welcome, next steps, and intake questionnaire link
3. Create three scheduled tasks in Make.com’s scheduler: Day 3 check-in email, Day 7 feedback email
4. Each scheduled email checks the project status first — if project is already marked Complete, skip the email

The Day 3 and Day 7 emails require Make.com’s Sleep module or a workaround using scheduled scenarios with date filters — Make’s Core plan is needed for scheduled scenarios that run at custom intervals. This full onboarding sequence, including what each email should say and how the project records connect, is covered in our guide to automating client onboarding as a freelancer.

Make.com Email Scenarios: Complexity vs. Time Saved

Common Mistakes When Building Email Scenarios in Make.com

Skipping the filter module

Every email scenario needs a filter between the trigger and the email action — otherwise you’ll send emails for events you didn’t intend to catch. A “watch Notion database” trigger fires for every change to every record, not just the ones that matter. Without a filter (Status = “Deliverable Sent” AND Client Email is not empty), you’ll send client notifications when internal records change, when test entries are created, or when you update your own admin notes. Add a filter module as the second step in every scenario before building anything else.

Not handling missing data

Make.com scenarios fail — not error, but silently stop — when a required variable is empty. If your Gmail module tries to send to {{contact.email}} and that field is empty in the source record, the scenario stops without sending anything and without flagging the failure prominently. Add an error handler to every scenario that involves sending email: if the email field is empty, create a task in ClickUp or Notion flagging the record as “Missing email — manual follow-up required.” This turns a silent failure into an actionable notification.

Extending Your Email Automation: What to Build After the Core Scenarios

Once the five core email workflows are running, two additional scenarios deliver outsized value for solopreneurs who publish content or run referral programs:

• Newsletter sent → social post created: When you send a newsletter through your email platform, Make.com detects the campaign via API, extracts the subject line and key paragraph, and creates a drafted social post in your content calendar database in Notion. This feeds your content pipeline without manual repurposing work.
• Referral received → thank-you email + tracking: When a new client mentions a referral source on their intake form, Make.com sends a thank-you email to the referring person automatically and creates a referral tracking record in Airtable. Most solopreneurs forget to follow up with referral sources — automation makes it consistent without adding a task to your list.

For a complete picture of what Make.com can automate beyond email — including client reporting, file management, and CRM updates — our roundup of the best Make.com automations for service businesses covers the full range of high-value scenarios.

Frequently Asked Questions

Does Make.com work with Gmail, or do I need a business email?

Make.com connects to both personal Gmail accounts and Google Workspace (business Gmail) accounts via OAuth. The connection process is identical for both — you authorize Make.com to access the account and it can both read and send email from that inbox. If you want emails to appear to come from a custom domain address (hello@yourbusiness.com), you need Google Workspace configured with that domain. Personal Gmail works fine for sending automation emails, but the “from” address will be your personal Gmail rather than a branded domain email.

How many email scenarios can I run on Make.com’s free plan?

Make.com’s free plan allows unlimited scenarios but caps total operations at 1,000 per month. Each action in a scenario (trigger check, filter evaluation, Gmail send, database update) counts as one operation. A typical email scenario with 4–5 modules uses 4–5 operations per run. If you run the scenario 50 times per month (50 new leads triggering intake responses), that’s 200–250 operations — well within the free tier. The free plan becomes restrictive when you have high-volume triggers or many scenarios running simultaneously; at that point, the Core plan at $10.59/month provides 10,000 operations.

What’s the difference between using Make.com for email versus using a dedicated email marketing platform?

Email marketing platforms (ConvertKit, Brevo, Mailchimp) excel at broadcasting to subscriber lists, managing opt-ins and unsubscribes, tracking open rates, and delivering drip sequences to large audiences. Make.com excels at triggered transactional emails — emails that fire in response to specific events in specific tools, with data pulled dynamically from your CRM or project management system. They serve different purposes and most solopreneurs use both: an email platform for newsletters and lead nurture sequences, Make.com for operational emails tied to business events. The overlap is minimal; the tools complement rather than replace each other.

Can Make.com send emails from my custom domain without Google Workspace?

If you use a custom domain email through a provider like Zoho Mail, Fastmail, or your hosting provider’s webmail, Make.com can connect via SMTP rather than the native Gmail module. The SMTP module lets you authenticate with any email provider that supports SMTP credentials — you enter the server address, port, username, and password, and Make.com sends through that account. Deliverability is generally slightly better through SMTP than through Gmail for high-volume sending, though for the volumes most solopreneurs run (under 200 automated emails per month), the difference is negligible.

How do I prevent my automated emails from looking automated?

Three things make automated emails feel personal: use the recipient’s first name (not full name) in the opening, write in plain text rather than HTML templates with headers and images, and include one specific detail from their inquiry or record (project type, stated timeline, company name) to prove the email references their situation. Make.com’s variable system pulls any field from your trigger data into the email body — if your intake form captures “Project Type,” including “Looking forward to learning more about your {{project.type}} project” in the opening line takes 10 seconds to configure and makes the email read like a hand-written response rather than a template blast.