📢 Disclosure: Contains affiliate links. We earn a commission at no extra cost to you.
📢 AdSense Ad Unit

Make.com is the most powerful no-code automation platform in 2026 — and you can start using it for free. This step-by-step tutorial takes you from zero to building your first working automation scenario in under 30 minutes. No coding required. We'll also cover the key concepts that separate Make.com beginners from power users.

⚡ What You'll Learn in This Tutorial

✅ Set up your free Make.com account
✅ Understand the core concepts: scenarios, modules, triggers, actions
✅ Build your first automation: Gmail → Google Sheets
✅ Learn: routers, filters, schedulers, and error handling
✅ 5 real-world scenario templates to copy
✅ How Make.com credits work

📌 Estimated time: 30-60 minutes to complete your first working scenario

Step 1: Set Up Your Free Make.com Account

Start at make.com and click "Get started free." You'll get:

  • ✅ 1,000 credits/month (permanently free)
  • ✅ 2 active scenarios
  • ✅ Access to all 3,000+ integrations
  • ✅ No credit card required
💡

Free vs Trial: Make.com doesn't have a time-limited free trial — the free plan is permanent. This means you can build and test automations indefinitely without any payment. When you're ready for more scenarios or credits, upgrade to Core ($9/month).

Create Your Free Make.com Account →

Step 2: Core Concepts — The 5 Things You Must Understand

🎬 1. Scenario

A scenario is your complete automation — the visual "map" of what happens, when it happens, and how data flows. Think of it as a recipe. One scenario can contain unlimited steps (modules).

📦 2. Module

Each step in your scenario is a module — a circle on the canvas. Modules represent one action: "Watch for new Gmail email," "Create a Google Sheet row," "Send a Slack message." Every module run costs 1 credit.

⚡ 3. Trigger

The first module in every scenario is the trigger — the event that starts the automation. Examples: "New email received," "New form submission," "New Shopify order," or a schedule ("Run every day at 9am").

⚙️ 4. Action

All modules after the trigger are actions — things Make.com does in response to the trigger. Create a record, send a message, update a field, call an API. You can chain as many actions as needed.

🗂️ 5. Data Mapping

When a module runs, it outputs data (e.g., email sender, subject, body). Data mapping means using that output as input in the next module. Example: take the email sender's name from your Gmail trigger and put it in the "Contact Name" field in HubSpot.

📢 AdSense (300×250)

Step 3: Build Your First Scenario — Gmail → Google Sheets

Let's build a real automation: When you receive a new email in Gmail with a specific label, log the sender, subject, and date to Google Sheets automatically. This is a classic beginner scenario that you'll use in real life.

📋 What You'll Need

• A Make.com account (free)
• A Gmail account
• A Google Sheets spreadsheet (create one with columns: Date, Sender, Email, Subject)

Creating the Scenario

  1. Click "Create a new scenario" from your dashboard
  2. Click the large "+" button in the center of the canvas
  3. Search for "Gmail" and select it
  4. Choose "Watch Emails" as your trigger module
  5. Connect your Gmail account — click "Add" and follow OAuth prompts
  6. Set the folder to "INBOX" (or a specific label)
  7. Set "Maximum number of emails" to 10 (how many to process per run)
  8. Click OK to save the trigger

Adding the Google Sheets Action

  1. Hover over the Gmail module and click the small "+" that appears to the right
  2. Search for "Google Sheets" and select it
  3. Choose "Add a Row" as the action
  4. Connect your Google account
  5. Select your spreadsheet and the Sheet tab
  6. Map the fields:
    • Column A (Date) → click the field → select Date from Gmail output
    • Column B (Sender) → select From: Name
    • Column C (Email) → select From: Email Address
    • Column D (Subject) → select Subject
  7. Click OK

Testing & Activating

  1. Click "Run once" at the bottom left — this tests your scenario once
  2. Check your Google Sheet — you should see your recent emails logged
  3. If it works: toggle the scenario ON using the switch at the bottom
  4. Set the schedule — click "Scheduling" and set how often Make.com checks for new emails (every 15 min on free, every 1 min on Core+)

🎉 Congratulations — You Just Built Your First Make.com Scenario!

This 2-module scenario costs 2 credits per email processed. With the free plan's 1,000 credits, you can process 500 emails before upgrading. For most users, the Core plan at $9/month (10,000 credits) handles thousands of emails per month.

Step 4: Understanding Data Mapping

Data mapping is what makes Make.com powerful. When any module runs, it creates a bundle of output data. The next module can use any piece of that data as its input.

When you click on a field in a module, you'll see a panel on the right showing all available data from previous modules. Click any item to insert it. You can also use formulas to transform the data:

  • {{formatDate(1.date; "DD/MM/YYYY")}} — format a date
  • {{upper(1.subject)}} — convert text to uppercase
  • {{substring(1.body; 0; 100)}} — take first 100 characters
  • {{if(1.score > 80; "Hot Lead"; "Cold Lead")}} — conditional text

Step 5: Adding Filters

Filters let you stop a scenario mid-run if conditions aren't met. Example: only proceed if the email is from a specific domain, or only if the order value is over $100.

To add a filter:

  1. Click the small wrench icon (⚙️) on the connection line between two modules
  2. Click "Set up a filter"
  3. Choose a field, an operator (equals, contains, greater than, etc.), and a value
  4. Click OK — the filter will now stop the run if the condition isn't met
📢 AdSense (300×250)

Step 6: Routers — Branching Logic

Routers are what separate Make.com from Zapier. A router splits your scenario into multiple branches that run in parallel. Example: if score > 80 → send to Sales; if score 40-80 → add to Newsletter; if score < 40 → do nothing.

To add a router:

  1. Click the "+" after any module
  2. Search for "Router" and add it
  3. Click the "+" on each output path of the router to add modules to that branch
  4. Click the wrench on each router output line to add a filter (the condition for that branch)
💡

Router tip: Make the last router branch have no filter — this becomes your "catch-all" or "else" path that runs when none of the other conditions match. This prevents records from being silently skipped.

Step 7: Scheduling Your Scenario

There are two ways a scenario can trigger:

  • Polling (Schedule-based): Make.com checks the trigger app at regular intervals (15 min on free, as low as 1 min on Core+). Good for: Gmail, RSS feeds, spreadsheets.
  • Webhook (Instant): The trigger app sends data to Make.com instantly when an event happens. Good for: form submissions, Stripe payments, custom code. Webhooks are faster and more credit-efficient.
🔑

Pro tip — Save Credits with Webhooks: Polling runs consume credits even when there's nothing new to process. Webhooks only fire when an event actually happens. Wherever possible, use webhook triggers (Typeform, Stripe, most modern apps support them) to dramatically reduce your credit consumption.

Step 8: Error Handling Basics

Unlike Zapier (which just stops and emails you), Make.com lets you define what happens when a module fails. Right-click any module → click "Add an error handler route." You can choose:

  • Resume: Ignore the error, continue with next item
  • Ignore: Skip this record entirely
  • Break: Stop the scenario run
  • Commit: Process all successful items, stop at the first error
  • Rollback: Undo all changes from this run (useful for database operations)

For production scenarios, always add a Slack notification or email on your error route so you know when something fails.

9 Ready-to-Use Scenario Templates

🟢 1. New form submission → Google Sheets + Email notification

Typeform/Tally → Sheets row + Gmail confirmation. Perfect for event registrations, contact forms.

🔵 2. New Shopify order → Slack alert + inventory check

Shopify → Slack notification + Google Sheets inventory update. E-commerce operations essential.

🟣 3. RSS feed → Twitter/LinkedIn auto-post

New blog post RSS → auto-create social media post. Content marketing automation.

🟠 4. Daily report from Google Analytics → Slack

Scheduled → pull GA4 data → format → post daily traffic summary to Slack channel.

🔴 5. New Gmail email from client → create task in ClickUp/Asana

Gmail filter → create task with email subject + body. Never miss a client request.

10. Understanding Make.com Credits

🧮 Credit Calculator

Standard rule: 1 module run = 1 credit

Example — Gmail → Sheets scenario (2 modules):
Processing 100 emails/month = 200 credits (well within free plan)
Processing 2,000 emails/month = 4,000 credits (Core plan needed)

Example — 5-step lead processing (5 modules):
500 leads/month × 5 modules = 2,500 credits (Core plan comfortable)

AI scenarios: AI module credit consumption varies based on token usage. Budget ~5-15 credits per AI call depending on prompt/response length.

11. Next Steps — Leveling Up

Once you've built your first scenario, here's how to go deeper:

  • 📚 Make.com Academy — free courses at academy.make.com
  • 🌐 Make Community — forum with 50,000+ users sharing scenarios
  • 🔧 Template Library — 1,000+ pre-built scenarios to copy and customize
  • 📖 Learn Iterators — for processing arrays (e.g., multiple Shopify line items)
  • 📊 Learn Aggregators — for combining data from multiple runs into one output
  • 🔗 Learn HTTP module — connect to any API without a pre-built integration
Start Building with Make.com Free →
Is Make.com easy to learn for beginners? +
Make.com has a moderate learning curve. The visual canvas feels overwhelming at first, but most beginners can build their first working scenario within 30-60 minutes using templates. Core concepts become intuitive within a week of use. It's harder to start than Zapier but much more powerful once you know it.
Do I need coding skills to use Make.com? +
No. Make.com is a no-code tool — zero programming required for 95% of scenarios. The formula system (for data transformations) has a syntax similar to Excel formulas. For advanced use cases like connecting to custom APIs via the HTTP module, basic understanding of REST APIs helps but isn't required.
What's the difference between Make.com and Zapier for beginners? +
Zapier uses a linear "trigger → action → action" structure that's very beginner-friendly. Make.com uses a visual canvas where you can build branching logic, loops, and parallel paths. For simple automations, Zapier is easier. For complex workflows and real-world business processes, Make.com is dramatically more capable. Cost-wise, Make.com is 70-80% cheaper for equivalent work.
📢 AdSense (Bottom)