Make.com Tutorial for Beginners: Build Your First Automation in 20 Minutes
Make.com has a learning curve that’s steeper than Zapier — but it’s also significantly more powerful and cheaper at scale. Once you understand the core concepts (modules, scenarios, operations), you can build automations that would be impossible or prohibitively expensive in Zapier.
This tutorial builds a real, useful workflow from scratch. By the end, you’ll have a working automation and the foundational knowledge to build more.
Make.com Core Concepts
Before touching the interface, understand three terms:
- Scenario: A complete automation workflow — like a flowchart of connected actions
- Module: An individual step in the scenario — one action in one app
- Operation: Every time a module runs (Make charges per operation, not per “task”)
A scenario with 3 modules running once = 3 operations. Make’s free plan includes 1,000 operations per month — roughly 330 complete 3-step runs.
What We’re Building
This tutorial builds a lead-capture automation:
- Someone submits your Google Form (lead form)
- Make creates a new contact in HubSpot CRM
- Make sends a welcome email via Gmail
- Make posts a notification to your Slack channel
What you need: Make.com account (free), Google account, HubSpot free account, Gmail account. Slack is optional.
Step 1: Set Up Your Google Form Trigger
Create the Scenario
- Log into Make.com → click “Create a new scenario”
- On the canvas, click the large “+” to add your first module
- Search for “Google Forms” → select “Watch Responses”
- Click “Add” to connect your Google account
- Select the form you want to monitor (or create a simple test form with name + email fields first)
- Set “Maximum number of returned results” to 1
- Click OK
This module will trigger the scenario every time someone submits your form.
Step 2: Add the HubSpot Module
- Click the “+” to the right of your Google Forms module
- Search for “HubSpot CRM” → select “Create a Contact”
- Connect your HubSpot account (click “Add” → authorize HubSpot)
- Map the form fields to HubSpot fields:
- Email → {{1. Email}} (the output from your Google Forms module)
- First Name → {{1. Full Name}} (or split if you have separate first/last fields)
- Click OK
The purple data bubbles (called “pills”) pull data from the previous module. Clicking inside any field shows all available data from earlier modules.
Step 3: Add the Gmail Module
- Click “+” after the HubSpot module
- Search for “Gmail” → select “Send an Email”
- Connect your Gmail account
- Fill in the fields:
- To: {{1. Email}} (from the form response)
- Subject: “Welcome to [Your Business Name]!”
- Content: Write your welcome message, using {{1. Full Name}} to personalize
- Click OK
Step 4: Test Your Scenario
- Click “Run once” (bottom left of the canvas)
- Submit your Google Form with a test name and email
- Return to Make — within 30 seconds, you should see green checkmarks on each module
- Click each module to verify the data: form captured → HubSpot contact created → Gmail sent
- Check your HubSpot contacts and your email inbox to confirm it worked
Step 5: Activate and Schedule
- Once the test passes, click the toggle at the bottom to activate the scenario
- Set the schedule: click the clock icon → choose how often Make checks for new responses
- For low-volume forms: every 15 minutes is fine and uses minimal operations
- For high-traffic forms: every 5 minutes ensures faster follow-up
Adding the Slack Notification (Optional)
- Click “+” after the Gmail module
- Search “Slack” → “Create a Message”
- Connect Slack and choose your notification channel
- Message: “New lead: {{1. Full Name}} ({{1. Email}}) — HubSpot contact created”
- Click OK → test again → activate
Your Completed Scenario
| Module | App | What It Does | Operations Used |
|---|---|---|---|
| 1 | Google Forms | Watch for new submissions | 1 per check + 1 per result |
| 2 | HubSpot | Create contact | 1 per new lead |
| 3 | Gmail | Send welcome email | 1 per new lead |
| 4 (optional) | Slack | Notify team | 1 per new lead |
What to Build Next
Now that you understand the basics, useful next scenarios include:
- Stripe payment received → Create project in ClickUp + send invoice to client
- New Typeform response → Add to Airtable → Send confirmation email
- New WordPress post → Generate social media captions via OpenAI → Add to Buffer queue
- Make.com scenarios are built by connecting modules — one per app action
- Data flows between modules using “pills” — clickable bubbles that reference previous module outputs
- Always test with “Run once” before activating a scenario
- Make’s free plan (1,000 ops/month) handles this 4-module scenario for ~250 new leads per month
- Webhook triggers fire instantly; Watch/poll triggers have a schedule delay
Frequently Asked Questions
Is Make.com better than Zapier for beginners?
Zapier is easier for complete beginners — its linear interface is more intuitive. Make has a steeper initial learning curve but is more powerful once you’re past the basics. If you’re comfortable with this tutorial, Make’s additional power becomes accessible quickly.
What if my scenario fails?
Make shows failed operations in your scenario history with error details. Common failures: expired app authorization (re-authenticate the connection), changed field names in the source app (update your mappings), or rate limits from the destination app (add a delay module). Make’s error notifications email you when scenarios fail repeatedly.
Can I use Make.com with apps not on their list?
Yes — the HTTP module lets you make API calls to any app with a public API. This requires more technical knowledge (reading API documentation, forming requests) but opens Make to virtually every software tool in existence.