Make.com Tutorial for Beginners: Build Your First Automation (2026)

Make.com lets you automate repetitive tasks between apps without writing code. This beginner’s guide walks you through building your first automation in under 30 minutes — starting with a free account and a real working example.

Some links on this page earn us a commission at no extra cost to you.

Last updated: March 2026

What Is Make.com? (60-Second Explainer)

Make.com is a visual automation platform that connects your apps and services so they can work together automatically. When something happens in one app (a form submission, a new email, a new order), Make.com can trigger a series of actions in other apps — without you having to manually copy, paste, or forward anything.

Key facts about Make.com:

• Connects 1,500+ apps including Google Workspace, Slack, HubSpot, Shopify, Mailchimp, Airtable, Salesforce, and hundreds more
• Visual canvas-based builder — you drag and connect modules rather than filling out linear forms
• Previously called Integromat, rebranded to Make.com in 2022
• Used by 500,000+ businesses worldwide
• Free plan available with 1,000 operations/month — no credit card required

If you’ve heard of Zapier, Make.com solves the same problem — automating repetitive tasks between apps — but with a more powerful visual interface and significantly lower pricing for the same capacity.

Key Concepts Before You Start

Make.com uses specific terminology that’s different from other automation tools. Understanding these five terms will make everything else click:

Scenario — This is your automation workflow. A scenario is the complete process from trigger to final action. Think of it as equivalent to a “Zap” in Zapier or a “Recipe” in IFTTT. You might have a scenario called “New Form Response → Google Sheets + Slack Alert.”

Module — Every step in a scenario is a module. The trigger is a module. Each action is a module. A 3-step scenario has 3 modules. Modules are represented as circular icons connected by arrows on the canvas.

Operation — This is Make.com’s billing unit. Every time a module executes, it consumes 1 operation. A 3-module scenario running once = 3 operations. Your plan determines how many operations you get per month (free = 1,000, Core = 10,000).

Connection — A connection is an authenticated link between Make.com and a specific account in an app. Before you can use Google Sheets in a scenario, you create a Connection that gives Make.com access to your Google account. You can have multiple connections per app (e.g., two different Google accounts).

Bundle — A bundle is a single record of data passing through your scenario. If a form gets 5 responses and your scenario runs, it processes 5 bundles (one per response). Each bundle execution consumes operations.

Setting Up Your Free Account

Getting started with Make.com is free and takes about 5 minutes:

1. Go to make.com and click “Get started free”
2. Sign up with email or Google account — no credit card required
3. Verify your email address
4. You’ll land on the Make.com dashboard with 1,000 free operations per month

Your free account includes access to all 1,500+ app integrations. The only limitation is the 1,000 operation monthly cap. For testing and learning, 1,000 operations is more than enough. When you’re ready for real business use, upgrade to Core for $9/month (10,000 operations).

Before building your first scenario: Set up the Connections you’ll need. Go to Connections in the left sidebar and connect Google (for Forms and Sheets) and Slack. Having these connected before you start scenario building means you won’t be interrupted mid-build to authenticate apps.

Your First Scenario — Google Form to Google Sheets + Slack Alert

We’ll build a real working automation: every time someone submits a Google Form, Make.com adds their response to a Google Sheet row and sends a Slack notification. This 3-module scenario is the perfect starting point because it’s genuinely useful and covers all the fundamentals.

Before you start: Create a Google Form with a few fields (Name, Email, and one more). Create a Google Sheet with matching columns. Have a Slack workspace ready with a channel for test notifications.

Step 1: Create a new Scenario

In your Make.com dashboard, click the blue “Create a new scenario” button in the top right. You’ll see a blank canvas with a large circle in the center — this is where you add your first module.

Step 2: Add the Trigger (Google Forms)

Click the large + circle in the center → a search box appears → type “Google Forms” → select “Google Forms” from the results → choose “Watch Responses” → click on the module to configure it → select your Connection (or create one if you haven’t) → select the form you created → click OK. The trigger module now shows the Google Forms icon.

Step 3: Run Once to Get Sample Data

Before adding more modules, you need sample data to map fields. Click “Run once” in the bottom left → go to your Google Form in another tab → submit a test response → return to Make.com → you’ll see a green bubble with “1” on the trigger module, indicating it captured 1 bundle of data. Click the bubble to see the response fields — you’ll see all your form field values mapped by name.

This sample data step is critical. Without it, you’ll have no fields to map in later modules.

Step 4: Add the Google Sheets Action

Click the + icon that appears to the right of your trigger module → search “Google Sheets” → select “Add a Row” → configure: choose your Connection → select your spreadsheet → select the sheet tab → for each column, click the field and select the matching form field from the dropdown (Make.com shows all the data from your sample response) → click OK.

Step 5: Add the Slack Notification

Click the + after the Sheets module → search “Slack” → select “Create a Message” → configure: choose your Slack Connection → select your target channel → in the Message field, type your notification text and insert mapped fields (click inside the text box and select fields from the dropdown — e.g., “New form response from [Name field]: [Email field]”) → click OK.

Step 6: Test the Full Scenario

Click “Run once” → submit another test form response → watch the scenario execute → verify: (1) a new row appeared in your Google Sheet with the correct data, and (2) the Slack message appeared in your channel. If either didn’t work, click on the module that failed — Make.com shows detailed error information to help you troubleshoot.

Step 7: Activate the Scenario

Once testing is confirmed, click the scheduling toggle at the bottom left → set to “Every 15 minutes” (or every 1 minute on the Pro plan) → click Activate. Your scenario is now live and will check for new form responses every 15 minutes around the clock.

Understanding Operations — Budgeting Your Free 1,000

Now that your 3-module scenario is active, here’s what it’s consuming:

• Each form response that comes in = 3 operations (1 per module)
• 1,000 free operations ÷ 3 modules = ~333 form responses before hitting the limit
• At 50 responses/month, your 1,000 ops covers 6+ months of this scenario
• At 200 responses/month, you’ll use 600 ops — leaving 400 for other scenarios

If you hit 1,000 operations on the free plan, your scenario pauses until the next month. To avoid this, upgrade to the Core plan at $9/month for 10,000 operations — enough for most small businesses’ full automation stack.

Pro tip: Enable email notifications for operation limit warnings in your Make.com account settings. You’ll get an alert when you’re approaching the limit rather than discovering your automations stopped after the fact.

Adding a Filter — Only Run When Conditions Are Met

Filters let you stop a scenario mid-execution when certain conditions aren’t met. This saves operations and prevents unnecessary actions.

Example: You only want to send the Slack alert when a form respondent rates their experience above 8/10.

1. Click the small wrench/spanner icon that appears between two modules on the arrow connecting them
2. Select “Set up a filter”
3. In the filter configuration, set: Label (e.g., “Score above 8”) → Condition: [Score field] → Greater than → 8
4. Click OK

Now the Slack module only executes when the score field exceeds 8. The Google Sheets row still gets added for every response (the filter sits between Sheets and Slack), but Slack only gets notified for high scores.

Filters don’t count as operations — they’re evaluated within the flow without consuming a billing unit. This makes them an efficient way to limit action modules to relevant events only.

Using the Router — Split Into Multiple Paths

The Router module lets you branch a scenario into multiple paths, each running different actions based on different conditions. This is Make.com’s equivalent of Zapier’s Paths feature — but more powerful.

Example: Form responses with score > 8 go to Path A (send to VIP list), responses with score 5-8 go to Path B (send to standard list), responses under 5 go to Path C (alert support team).

1. Click the + after your trigger → search “Router” → add it
2. The Router module shows multiple outgoing connections
3. Add a module on each branch (Path 1, Path 2, Path 3)
4. Click the filter icon on each branch to set the condition for that path

Multiple paths can run simultaneously for the same bundle — if a record meets conditions on both Path 1 and Path 2, both paths execute. Use exclusive conditions (mutually exclusive ranges) to ensure only one path runs per bundle.

5 Beginner Scenarios to Try After This

Once you’ve mastered the Google Forms → Sheets + Slack setup, these are the next most useful scenarios to build:

• Typeform → Google Sheets: Same as your first scenario but using Typeform instead of Google Forms. Good practice for connecting a different form tool.
• New Shopify order → Slack notification: Trigger on Shopify “Watch Orders” → Slack “Create a Message.” Useful for real-time order alerts.
• Gmail email labeled “lead” → HubSpot contact: Trigger on Gmail “Watch Emails” with label filter → HubSpot “Create a Contact.” Automates CRM entry from email.
• Google Calendar event → Slack reminder 1 hour before: Trigger on Google Calendar “Watch Events” → Sleep module (calculate time offset) → Slack message. Requires a bit more setup but very useful.
• RSS feed → Slack channel: Trigger on RSS “Watch RSS Feed Items” → Slack “Create a Message.” Perfect for monitoring competitor updates or industry news.

Common Beginner Mistakes to Avoid

These are the errors most beginners make in their first week with Make.com:

• Not running “Run once” before activating: Without sample data, you can’t map fields in action modules. Always run once and get a test response before building action steps.
• Forgetting to set a schedule: A scenario that’s been built and tested but never activated with a schedule won’t run automatically. Don’t forget to toggle Scheduling and set an interval.
• Mapping the wrong fields: When you have multiple similar fields (first name, last name, full name), it’s easy to map the wrong one. Double-check your field mappings after testing by reviewing the actual output in your destination app.
• Not setting up error notifications: Go to your scenario settings and enable email notifications for errors. When an API permission changes or a destination app rejects data, you’ll know immediately rather than discovering the issue days later.
• Building too-complex scenarios before mastering the basics: Start with 2-3 module scenarios and build up. Trying to build a 7-module scenario with a router and multiple filters before you understand the basics leads to confusion and wasted time.

Ready to go deeper? Read our full Make.com review for a comprehensive feature assessment. See our Make.com vs Zapier comparison if you’re evaluating both platforms. Check our Make.com pricing guide to understand which plan you need. And if you’re migrating from Zapier, our migration guide walks you through the whole process.