Quick Picks (TL;DR)
- Make is the best no-code automation tool for people who want visual control over complex, multi-step workflows
- Ideal for freelancers and small teams who have outgrown Zapier but are not ready to write code
- Free plan includes 1,000 operations/month — enough to learn and run lightweight automations
Why Make Clicked for Me (and Why It Might for You)
I tried Make for the first time after hitting Zapier's pricing wall on a client project. The visual canvas — where you literally drag and connect modules on a screen — changed how I thought about automation. Instead of filling out forms left to right, I was drawing data pipelines. Something about that made logic errors obvious in a way that list-based tools never did.
If you are a freelancer, solo founder, or small-team operator who wants real automation power without hiring a developer, Make is worth the learning curve. This guide will walk you from zero to your first live scenario.
What Is Make (Formerly Integromat)?
Make rebranded from Integromat in 2022. The core product stayed the same: a visual workflow automation platform that lets you connect apps, transform data, and run logic — all without writing code.
The key concepts:
- Scenario — Make's word for a workflow or automation
- Module — An action tied to a specific app (e.g., "Watch new Gmail emails" or "Add Airtable row")
- Operation — One module execution; your plan's usage is measured in operations
- Trigger — The module that starts the scenario (scheduled or instant)
Comparison: Make vs. the Alternatives
| Tool | Best for | Free plan | Starting price | Standout |
|---|---|---|---|---|
| Make | Visual, complex multi-step flows | Yes (1,000 ops/mo) | ~$9/mo (verify) | Canvas editor + data mapping |
| Zapier | Quick, simple two-app connections | Yes (100 tasks/mo) | ~$20/mo (verify) | 6,000+ app integrations |
| n8n | Self-hosted power users | Yes (self-host) | ~$20/mo cloud (verify) | Open source, full control |
| Pipedream | Developer-friendly event streams | Yes | ~$19/mo (verify) | Code + no-code hybrid |
| Pabbly Connect | Budget teams with high volume | No | ~$19/mo (verify) | Unlimited tasks on paid plans |
Step 1: Create Your Make Account
Go to make.com and sign up for the free plan. No credit card required. Once inside, you land on the dashboard where your scenarios will live.
The interface has three main areas:
- Left sidebar — Scenarios, templates, connections, team settings
- Scenario canvas — The drag-and-drop workspace
- Right panel — Module configuration when you click a module
Take five minutes to poke around before building anything. Familiarity with the layout saves frustration later.
Step 2: Connect Your First Apps
Before building a scenario, you need to authorise Make to access your apps. Go to Connections in the left sidebar and add the apps you plan to use.
Common first connections for beginners:
- Google Sheets or Airtable (data destination)
- Gmail or Outlook (email trigger)
- Typeform or Jotform (form trigger)
- Slack or Discord (notification output)
Each connection walks you through an OAuth flow — you click "Authorise", log into the app, and approve permissions. Make stores the token so you do not have to re-authenticate every scenario.
Tip: Connect at least two apps before building. Trying to add connections mid-build slows you down.
Step 3: Build Your First Scenario
Click Create a new scenario. The canvas opens with a large plus button in the centre. That is your first module slot.
For a beginner-friendly first scenario, try this: Google Form submission → Google Sheets row.
- Click the plus, search for "Google Forms", select Watch responses
- Choose your connection, pick the form, set interval to 15 minutes
- Click the circle after that module to add a second module
- Search "Google Sheets", select Add a row
- Map the form fields to the correct columns — Make shows you the available data from step 1 as variables you can drag in
Click Run once in the bottom toolbar to test with live data. Make will execute the scenario once and show you each module's input and output. Green bubbles mean success. Click any bubble to inspect the exact data that flowed through.
Step 4: Understand the Data Flow
Make's superpower is data transformation. Between modules you can add a Tools module to:
- Format dates into any pattern
- Convert text to uppercase/lowercase
- Parse JSON or XML
- Do basic math on numeric fields
- Set variables for reuse later in the scenario
You can also add Filters between modules — a condition that must be true for execution to continue. For example: "Only proceed if the email address contains @company.com." This is the equivalent of an if-statement without writing code.
Router modules split the flow into parallel branches, each with its own filter. This is where Make genuinely surpasses Zapier for complex logic.
Step 5: Schedule and Activate
By default, scenarios run on a schedule (every 15 minutes is the starting point). You can set this from 1 minute up to once a month depending on your plan.
For instant triggers — a webhook, a form submit, a new message — Make can respond within seconds. Enable instant triggers in the module settings if the app supports them.
Once you are satisfied with a test run, flip the toggle in the bottom-left from OFF to ON. Your scenario is now live.
Common Beginner Mistakes to Avoid
- Skipping the test run. Always click "Run once" before activating. Silent errors in unmapped fields will cause data loss.
- Ignoring error handlers. Add an error route to your scenario so failures send a Slack or email alert rather than silently dying.
- Over-engineering too early. Start with a two-module scenario. Add complexity once the basic flow is reliable.
- Hitting operation limits without realising. Watch your monthly usage in the dashboard. A misconfigured trigger polling every minute will burn through 43,200 ops/month.
How to Choose Between Make and Zapier
Use Make if you need conditional branching, data transformation, or plan to automate more than a handful of simple tasks. The learning curve pays off within a week.
Use Zapier if you want something live in 10 minutes and your workflow is a straight line from trigger to action. The wider app library also matters if you rely on niche tools.
In my experience, most teams end up using both: Zapier for quick integrations with uncommon apps, Make for the workflows that actually need to be reliable and maintainable.
FAQ
Q: Is Make actually free to start? Yes. The free plan gives you 1,000 operations per month, two active scenarios, and 15-minute minimum scheduling intervals. That is enough to run a few real workflows and decide if a paid plan makes sense.
Q: How hard is Make to learn compared to Zapier? Expect a 2-3 hour investment to get comfortable. The visual canvas is intuitive once it clicks, but the first hour can feel overwhelming. Most beginners find it easier than expected after completing their first working scenario.
Q: Can Make handle webhooks? Yes. Make has excellent webhook support — you can create a custom webhook URL as a trigger, and any app that can send HTTP POST requests can fire your scenario instantly.
Q: What happens if a scenario fails? Make logs the error with full input/output details so you can diagnose the issue. If you have set up an error handler module, it can notify you via Slack, email, or any other connected app. Failed operations do not count against your monthly quota.