Photo by Daniil Komov on Pexels

Make.com Tutorial for Beginners: Your First Automation

By Kevin Amayi · May 10, 2026 · 10 min read

A client needed a weekly report compiled and sent before their Monday morning meeting. The raw data lived in three places — a form response spreadsheet, a CRM export, and an email chain. Manually assembling it took about two hours every Sunday. I set up a Make.com automation in less than 30 minutes. It ran the same job while I slept, every week, for eight months without a single failure.

This Make.com tutorial for beginners starts with the fundamentals and ends with a working automation. Make.com is a visual no-code tool. You connect apps by dragging modules onto a canvas, link them together, and define what triggers the flow. When something happens in one app, Make.com tells another app what to do about it. No code is involved unless you want it to be.

By the end, you’ll have a live automation running on the free plan and a clear picture of where to go next.

What Is Make.com and How Does It Work?

Make.com is an app integration and automation platform. You build scenarios — visual flowcharts where data moves from one app to another based on triggers you define. Each step in a scenario is called a module. The first module is always a trigger; everything after it is an action.

Before Make.com was called Make.com, it was called Integromat. The rebrand happened in 2022. If you searched for “Integromat tutorial” and ended up here, you’re in the right place — same platform, different name, slightly updated interface.

Make.com supports over 1,000 app integrations, including Gmail, Google Sheets, Slack, Notion, Airtable, HubSpot, and Stripe. Additionally, if a service offers a public API, Make.com can connect to it via a custom HTTP module — so you’re rarely blocked by a missing native integration.

Make.com is not a database, a backend, or a replacement for custom software. It is a connector. The moment you find yourself spending more than a few minutes each week moving data between tools you already use, Make.com is worth looking at.

Setting Up Your Make.com Account

Go to make.com and create a free account with your email address. After email verification, you land on the Make.com dashboard. On the left side, you’ll see your scenario list. In the center, there’s a “Create a new scenario” button — that’s where you’ll spend most of your time for the first few weeks.

The free plan is more useful than most free tiers. Specifically, it includes:

• 1,000 operations per month
• 2 active scenarios
• 15-minute minimum execution interval
• Access to all 1,000+ app integrations
• 30-day execution history
• Unlimited inactive scenario storage

The important point is that all integrations are available on the free plan. Make.com does not lock Gmail, Slack, or HubSpot behind a paywall. The constraints are on volume — how many times your scenarios run — and frequency — how often they check for new data. For a beginner building a first automation, neither limit is a problem.

Once your account is active, connect the apps you plan to use first. Go to your profile, find “Connections,” and authenticate each service. OAuth handles authentication for most apps — you click, approve, and Make.com stores the connection securely. You do this once per app, not once per scenario.

Your First Make.com Scenario: Step-by-Step

A good first scenario has one trigger and one action. This one watches your Gmail inbox for emails with a specific label and logs the sender, subject, and date as a new row in Google Sheets. It is simple enough to build in 15 minutes and useful enough that you’ll actually keep it running.

1. Click “Create a new scenario” from your dashboard
2. Click the large “+” circle on the canvas to add your first module
3. Search for “Gmail” and select it from the list
4. Choose the trigger: Watch Emails
5. Select the connection you set up earlier, or authenticate your Google account now
6. Set the label to watch — create a label called “To Log” in Gmail if you don’t have one
7. Click the small “+” at the edge of the Gmail module to add a second module
8. Search for “Google Sheets” and select Add a Row
9. Select the same Google account, then choose or create a spreadsheet
10. Map the fields: drag Subject to Column A, From to Column B, Date to Column C
11. Click “Run once” to test — apply the label to a real email in Gmail first
12. Confirm that a new row appears in your spreadsheet
13. Click the toggle in the bottom-left corner to activate the scenario

Make.com will now check your Gmail every 15 minutes on the free plan. Any email with that label gets logged automatically. You do not need to do anything else.

The first time you run a test and watch data move from Gmail to Google Sheets in real time — without a single line of code — you will feel something between satisfaction and mild disbelief. Both are appropriate.

For a comparison of how Make.com’s approach differs from a more technical automation tool, the n8n vs Make.com comparison breaks down the trade-offs in detail.

Understanding Modules, Triggers, and Filters

Once you’ve built one scenario, you’ll want to build more complex ones. Six concepts determine how far you can go:

Filters are where most beginners save the most time. Instead of building separate scenarios for every variation of a task, you build one scenario and add a filter that restricts which data moves through. Fewer scenarios means less maintenance and fewer operations consumed per month.

Routers become useful once you need to send data to different places depending on its content. The visual canvas makes branching logic readable — you can see every path the data takes without digging through nested conditionals in code. That clarity is the main reason a Make.com tutorial for beginners focuses on the canvas rather than configuration panels.

Make.com Pricing: Free vs Paid Plans

Make.com pricing is based on the number of operations per month, not the number of apps you connect or scenarios you build. All plans include all integrations. The differences between plans are operations per month, how many scenarios can be active simultaneously, and the minimum execution interval.

*Annual billing. Monthly billing is approximately 30% higher. Check make.com/en/pricing for current rates — pricing changes periodically and the figures above are approximate.

For a beginner, the free plan works until one of three things happens: you hit 1,000 operations, you need more than 2 active scenarios, or you need scenarios to run more frequently than every 15 minutes. Core at approximately $9/month resolves all three constraints.

Pro adds full execution history, custom variables, and priority support. These matter once you’re managing several complex automations. They’re not necessary at the start. If you’re deciding between Make.com and a self-hosted alternative, the n8n tutorial for beginners covers what the self-hosted approach looks like in practice.

The Real Case for Automating Early

“Spending a day on tooling setup that saves ten minutes a week is not a good trade.” That is true. Make.com is rarely a day’s work, though — and the right automations save considerably more than ten minutes.

Consider the math on the Gmail-to-Sheets example. If manually logging each email takes 30 seconds, and 100 emails come in per month with that label, that’s 50 minutes of manual work. Make.com handles those 100 runs for 200 operations — well within the free tier. The setup takes 15 minutes once. The scenario runs indefinitely.

The same logic applies to moving form responses to a spreadsheet, sending Slack notifications when Airtable gets a new row, or creating calendar events from email confirmations. These are 15-to-30 minute builds that run indefinitely. The error rate is also zero, which manual processes cannot offer.

The right question is not “should I automate this?” but “does this happen often enough to justify 30 minutes of setup?” If the answer is yes more than once a week, automate it. If it happens twice a year, write it down and move on. For automations that grow beyond Make.com’s visual model, the n8n automation workflow tutorial covers what a code-first approach looks like.

When NOT to Use Make.com

Make.com solves a specific kind of problem. It is not the right tool for everything. Here are four situations where you should use something else:

• You need real-time response. The free plan checks for new data every 15 minutes. Even on paid plans, the minimum interval is 1 minute. If you need sub-second processing — payment confirmations, live chat routing, real-time dashboard updates — Make.com is not built for that. Use a backend with event-driven architecture instead.
• Your logic is complex enough to write tests for. A scenario with 12 modules, nested filters, and multiple routers is effectively a codebase. It happens to live on a visual canvas, but it behaves like code and needs to be maintained like code. At that point, you’ll spend more time debugging visual logic than you would writing an actual application. Move the logic to a proper codebase.
• Your data cannot leave your servers. Make.com processes data on its own infrastructure. If you handle medical records, certain financial data, or anything subject to strict data residency requirements, verify Make.com’s compliance certifications before routing sensitive data through it. For data that must stay in-house, n8n self-hosted is the stronger alternative — it runs on your own server and keeps all data within your control.
• You need a one-time data migration. Make.com is built for ongoing automation, not bulk one-off operations. If you need to move 50,000 rows from one system to another once, write a script. Using Make.com for a one-time task consumes your monthly operations without producing anything reusable.

Conclusion

That client’s weekly report ran on Make.com for eight months without a single failure. Two hours of manual work every Sunday, gone. The client never asked how it worked. That is the right outcome — good automation is invisible.

Key takeaways from this Make.com tutorial for beginners:

• Make.com connects apps visually — no code required for basic to intermediate automations
• The free plan gives you 1,000 operations/month and access to all 1,000+ integrations
• Start with a two-module scenario: one trigger, one action
• Add filters to restrict data flow; add routers when data needs to go to different places
• Upgrade to Core when you hit the 2-scenario limit or need faster than 15-minute intervals
• Use a different tool when logic is complex enough to test, data must stay in-house, or the task is a one-off

One final note: Make.com’s free plan does not expire. Which is either a genuinely generous business model or a very patient acquisition strategy. Either way, it is a reasonable place to start.

Frequently Asked Questions