Beginner Tutorial: Automate Sending Emails with Make.com (Step-by-Step)

Beginner Tutorial: Automate Sending Emails with Make.com (Step-by-Step)

Automating emails is one of the fastest ways to save time, increase consistency, and reduce manual follow-ups—especially if you send repetitive messages like lead replies, onboarding sequences, order updates, meeting confirmations, or internal notifications. In this beginner-friendly guide, you’ll learn how to automate sending emails with Make.com (formerly Integromat) from scratch, even if you’ve never built an automation before.

This tutorial is written for absolute beginners and includes practical examples, best practices, troubleshooting tips, and SEO-friendly structure so you can use it as a reference as you build real workflows.

What Is Make.com and Why Use It for Email Automation?

Make.com is a visual automation platform that connects apps (like Google Sheets, Airtable, Webhooks, Shopify, WordPress, HubSpot, and many more) to create automated workflows called scenarios. You can trigger a scenario when something happens (a new form submission, a new row added, a payment received) and then run actions like sending an email, saving data, or notifying a team.

Key benefits of automating email sending with Make.com

• Speed: Send confirmation or follow-up emails instantly.
• Consistency: Use the same reliable template every time.
• Personalization: Insert customer name, order details, or custom fields dynamically.
• Error reduction: Reduce missed follow-ups and manual copy/paste mistakes.
• Scalability: Handle 10 or 10,000 emails without changing your process.

Who This Make.com Email Automation Tutorial Is For

This guide is ideal if you are:

• A beginner who wants to learn Make.com fundamentals through a real use case
• A freelancer or agency automating client communication
• A small business owner needing automatic confirmations and follow-ups
• A creator handling newsletter sign-ups and onboarding messages
• A team automating internal alerts (e.g., “New lead received”) via email

Before You Start: What You Need

To follow along, prepare the following:

• A Make.com account
• Access to an email provider you can send from:
  • Gmail / Google Workspace
  • Microsoft 365 / Outlook
  • SMTP (custom email server)
  • Make’s built-in “Email” module (simple sending)
• A source of data to trigger the automation (choose one):
  • Google Sheets
  • Typeform / Google Forms
  • Airtable
  • Webhook (best for websites)

Core Concepts: Triggers, Actions, and Mapping (Make.com Basics)

If you’re new to Make.com, here are the three concepts you must understand to automate sending emails:

1) Trigger module

A trigger starts the scenario. Example triggers include:

• “Watch new rows” in Google Sheets
• “New form response” in Typeform
• “Custom webhook” (receives data from your website)

2) Action module

An action is what Make.com does after the trigger runs. In this tutorial, our main action is Send an email.

3) Mapping (dynamic fields)

Mapping is inserting data from the trigger into the email. For example:

• Recipient email address from a form response
• First name from a spreadsheet column
• Order ID or appointment time from your app

Choosing the Best Email Module in Make.com (Gmail vs SMTP vs Email)

Make.com offers several ways to send emails. Choosing the right method depends on your setup and deliverability needs.

Option A: Gmail / Google Workspace module

• Best for: beginners, small volumes, internal notifications, simple outreach
• Pros: easy authentication, familiar, fast setup
• Cons: Gmail sending limits apply; deliverability for marketing emails may be limited

Option B: Microsoft 365 / Outlook module

• Best for: business teams using Microsoft accounts
• Pros: strong business integration
• Cons: permissions and tenant settings can add complexity

Option C: SMTP module

• Best for: custom domains, transactional email, more control
• Pros: works with many providers (SendGrid, Mailgun, Amazon SES, your mail server)
• Cons: requires SMTP settings; deliverability depends on your provider and DNS setup

Option D: Make “Email” module (built-in)

• Best for: simple system notifications and testing
• Pros: quick, no extra accounts needed
• Cons: limited customization vs dedicated providers; not ideal for high-volume sending

Example Automation #1 (Beginner-Friendly): Send an Email When a New Row Is Added in Google Sheets

This is one of the most beginner-friendly Make.com email automations because it’s easy to visualize: add a row in Sheets → Make.com detects it → sends an email.

Step 1: Create your Google Sheet

Create a spreadsheet with these columns:

• Email (recipient email address)
• FirstName (for personalization)
• Topic (optional)
• Status (optional: e.g., “Pending”, “Sent”)

Example row:

• Email: example@domain.com
• FirstName: Alex
• Topic: Demo Request
• Status: Pending

Step 2: Create a new scenario in Make.com

In Make.com:

1. Go to Scenarios → Create a new scenario
2. Search for Google Sheets
3. Select Watch Rows (or “Watch New Rows”, naming can vary)
4. Connect your Google account

Step 3: Configure the Google Sheets trigger

• Select the spreadsheet and sheet
• Set the “Limit” to a reasonable number for each run (e.g., 1–10)
• Choose where it starts reading (often “From now on” for testing)

Step 4: Add the email sending module

Click the plus icon to add the next module and choose one:

• Gmail → Send an email, or
• Email → Send an email, or
• SMTP → Send an email

Step 5: Map fields into your email

In the email module, configure:

• To: map the “Email” column from Google Sheets
• Subject: e.g., Thanks for reaching out, {{FirstName}}!
• Body: write a message and insert mapped fields

Example email body (plain text):

Hi {{FirstName}},

Thanks for your message about {{Topic}}.

This is an automated confirmation that we received your request.

We’ll get back to you within 24 hours.

Best regards,

Your Name

Step 6 (Recommended): Update the Sheet status to “Sent”

To avoid sending duplicate emails, add one more module:

• Google Sheets → Update a Row
• Set Status to “Sent”

Step 7: Test and turn on the scenario

1. Click Run once
2. Add a new row in Google Sheets
3. Check Make.com execution details
4. Confirm the email is delivered
5. Turn the scenario ON and set a schedule (e.g., every 1–5 minutes)

Example Automation #2: Send a Welcome Email from a Webhook (Best for Websites)

If you have a website form (custom, WordPress, Webflow, etc.), a Webhook is often the best trigger. It allows your site to send form data to Make.com instantly.

Step 1: Create a “Custom webhook” trigger

1. Create a scenario
2. Select Webhooks → Custom webhook
3. Click Add and name it (e.g., “Website Lead Form”)
4. Copy the webhook URL

Step 2: Send sample data to the webhook

To let Make.com “learn” the data structure, send a test payload from your form or a tool like Postman. A typical JSON payload might look like:

{

  "email": "alex@example.com",

  "first_name": "Alex",

  "source": "Homepage form",

  "message": "Can you share pricing?"

}

Once Make.com receives it, it will generate fields you can map into the email.

Step 3: Add an email module and map the fields

In the email module:

• To: map email
• Subject: Welcome, {{first_name}} — we received your message
• Body: include {{message}} and next steps

Step 4 (Optional): Add spam protection logic

Website forms can receive spam. Add a filter step (or a router) to block obvious spam signals:

• Empty first name
• Message contains suspicious keywords
• Email domain is invalid

How to Write High-Converting Automated Email Templates

Email automation is not only technical—it’s also about clear, helpful messaging. Here are practical tips to create effective automated emails.

Use a clear subject line

• Good: “We received your request, Alex”
• Good: “Your booking is confirmed for Tuesday”
• Avoid: “Hello” or “Important” (too vague)

Keep the first line human

Even if the email is automated, it should feel personal and direct. Use the recipient’s first name where appropriate (without overdoing it).

Set expectations

Tell them what happens next:

• When you will respond
• What information they should prepare
• Where they can find resources in the meantime

Add a simple call-to-action (CTA)

Examples:

• “Reply to this email with your preferred time.”
• “Book a slot here: [link]”
• “Confirm your email by clicking [link].”

Make.com Email Personalization: Common Fields to Map

Most automated emails become significantly more effective when you insert real data from your trigger. Common personalization fields include:

• First name / last name
• Company name
• Order number or invoice number
• Appointment date and time
• Product name
• Support ticket ID
• Form message content

Adding Conditional Logic (Filters) Before Sending Emails

Filters help you avoid sending the wrong email to the wrong person. In Make.com, you can add a filter between modules.

Common filter examples

• Send only if Status = Pending
• Send only if Email is not empty
• Send only if Country = US (regional offers)
• Send only if LeadScore > 50 (high-intent leads)

How to Prevent Duplicate Emails in Make.com

Duplicate sends are one of the most common beginner issues. Here are the best ways to prevent them:

1) Mark records as “Sent”

After sending, update your database/spreadsheet field to “Sent”. Then filter future runs to only send when “Pending”.

2) Use unique IDs and data stores

If your trigger doesn’t have a built-in “processed” state, store processed IDs in a Make.com Data Store or your database.

3) Use “From now on” correctly

When setting up a watcher module, Make.com often lets you choose where to start. For existing datasets, starting from the beginning can cause a bulk send. For production, you typically want From now on or carefully controlled reprocessing.

Formatting Emails: Plain Text vs HTML Emails in Make.com

Depending on the module you use, you may be able to send HTML formatted emails. HTML emails allow brand styling, buttons, and better structure.

Plain text emails

• Pros: highest compatibility, simple, often feels more personal
• Cons: limited design

HTML emails

• Pros: branding, layout, CTA buttons, structured sections
• Cons: can break in some email clients if too complex

Beginner-friendly HTML email template (simple + compatible)

You can paste something like this into an HTML body field (if supported by your email module):

<div style="font-family: Arial, sans-serif; line-height: 1.6; color: #111;">

  <h2 style="margin: 0 0 12px;">Thanks, {{FirstName}}!</h2>

  <p style="margin: 0 0 12px;">

    We received your request about <strong>{{Topic}}</strong>.

  </p>

  <p style="margin: 0 0 16px;">

    We’ll reply within 24 hours. If it’s urgent, reply to this email with “URGENT” in the subject.

  </p>

  <a href="https://example.com/book" 

     style="display: inline-block; padding: 10px 14px; background: #111; color: #fff; text-decoration: none; border-radius: 8px;">

    Book a time

  </a>

  <hr style="border: none; border-top: 1px solid #e5e5e5; margin: 18px 0;">

  <p style="font-size: 12px; color: #555; margin: 0;">

    You’re receiving this email because you contacted us via our website.

  </p>

</div>

Note: For real production HTML emails, keep styling inline, avoid heavy CSS, and test in common clients (Gmail, Outlook, iOS Mail).

Example Automation #3: Send an Email When a New Typeform Response Arrives

If you’re collecting leads through Typeform, Make.com can automatically send a confirmation email (or notify your team) right after submission.

High-level scenario flow

1. Typeform: Watch responses
2. Email provider: Send an email to the respondent
3. (Optional): Send a notification email to your team
4. (Optional): Save response to Google Sheets/Airtable/CRM

Best practice: confirm + notify

• Confirmation email: builds trust and sets expectations
• Internal notification: ensures fast follow-up

Adding Attachments (Invoices, PDFs, or Files) to Automated Emails

Make.com can send attachments if the email module supports it. Common use cases include:

• Automatically emailing a PDF invoice
• Sending a generated report
• Sending a contract or onboarding PDF

How attachments typically work

1. Retrieve the file from a source (Google Drive, Dropbox, HTTP download, etc.)
2. Map the file into the email module’s attachment field

If you’re generating a PDF from data, you might use a document generator service, then fetch the file URL and attach it.

Using Routers in Make.com to Send Different Emails Based on Conditions

A Router splits your scenario into multiple paths. This is perfect for sending different email templates based on user choice.

Router example: different templates for different topics

• If Topic = “Pricing” → send pricing email
• If Topic = “Support” → send support acknowledgement
• If Topic = “Partnership” → send partnership follow-up

Each route can have its own filter and email module.

Scheduling: Instant vs Batch Email Sending

Make.com scenarios can run on schedules. Choosing the right schedule improves reliability and cost control.

Instant (webhook-based)

• Best for: real-time confirmations and time-sensitive follow-ups
• Behavior: runs immediately when data arrives

Every X minutes (watcher-based)

• Best for: spreadsheets and systems that don’t push events
• Behavior: checks for new items at intervals (e.g., every 1, 5, 15 minutes)

Batch sending

• Best for: daily summaries or digest emails
• Behavior: aggregates data and sends one email

Email Deliverability Basics (So Your Automated Emails Don’t Land in Spam)

Automation is easy—deliverability is what makes it effective. Here are beginner-friendly practices to improve inbox placement.

Use a domain email address when possible

Sending from a professional domain (like you@yourdomain.com) often performs better than a free address for business communication.

Set up SPF, DKIM, and DMARC (important for custom domains)

If you send from your own domain using SMTP or an email provider, configure:

• SPF (authorizes sending servers)
• DKIM (signs messages)
• DMARC (policy + reporting)

These DNS records reduce spoofing risk and can help prevent spam filtering.

Avoid spammy language

• Avoid excessive CAPS, too many exclamation marks, and aggressive marketing phrases
• Keep messages clear, relevant, and consistent with what the user requested

Don’t attach large files unnecessarily

Large attachments can increase spam suspicion and reduce deliverability. Consider sharing a link to the file instead.

Logging, Error Handling, and Monitoring in Make.com

Production automations should be observable. Make.com provides execution logs that show each step, inputs, outputs, and errors.

What to monitor

• Scenario execution history (did it run?)
• Module errors (authentication failed, rate limit, invalid email)
• Data mapping issues (blank fields)

Add a fallback notification for failures

A common best practice is to send yourself an internal email (or Slack message) when the scenario fails, including the error details and payload.

Common Make.com Email Automation Mistakes (and How to Fix Them)

Mistake 1: Email address field is empty or malformed

Fix: Add a filter: send only if Email contains “@” and is not empty. For stricter validation, use regex if needed.

Mistake 2: Duplicate sends

Fix: Use a “Sent” status field or store processed IDs. Avoid reprocessing old records unintentionally.

Mistake 3: Wrong mapping (first name appears as blank)

Fix: Re-run the trigger module to refresh sample data, then re-map fields. Ensure the trigger receives complete data.

Mistake 4: Scenario runs but email never arrives

Fix: Check spam folder, check sending limits, verify “From” address permissions, and confirm the email