Quick Picks (TL;DR)

Make is the strongest choice for freelancers and small teams who need conditional branching, data transformation, or multi-step logic — and the free plan's 1,000 operations/month is enough to build and test real automations before spending a cent. The critical caveat: a misconfigured trigger set to poll every minute consumes 43,200 operations in a single month, so understanding how operation counting works is not optional before you go live.

What Is Make (Formerly Integromat)?

Make rebranded from Integromat in 2022. The core product stayed the same: a visual automation platform that connects apps, transforms data, and runs conditional logic — no code required.

Four terms you need before touching the canvas:

  • Scenario — Make's name for a workflow or automation
  • Module — One action tied to a specific app (e.g., "Watch new Gmail emails" or "Add Airtable row")
  • Operation — One module execution; your plan's monthly limit is measured in operations, not scenarios
  • Trigger — The module that starts the scenario, either on a schedule or instantly via webhook

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 Canvas editor + data mapping
Zapier Quick, simple two-app connections Yes (100 tasks/mo) ~$20/mo 6,000+ app integrations
n8n Self-hosted power users Yes (self-host) ~$20/mo cloud Open source, full control
Pipedream Developer-friendly event streams Yes ~$19/mo Code + no-code hybrid
Pabbly Connect Budget teams with high volume No ~$19/mo Unlimited tasks on paid plans

Make's ~$9/mo entry price is roughly half of what Zapier charges to unlock multi-step automation. The trade-off is a steeper learning curve upfront.

Step 1: Create Your Account

Go to make.com and sign up for the free plan. No credit card required. The dashboard has three areas you will use constantly:

  • Left sidebar — Scenarios, templates, connections, team settings
  • Scenario canvas — The drag-and-drop workspace where modules connect graphically
  • Right panel — Module configuration, opened by clicking any module on the canvas

Spend five minutes clicking through the sidebar before building. Knowing where connections and scenario history live prevents confusion once you are mid-build.

Step 2: Connect Your Apps Before Building

Go to Connections in the left sidebar and authorize every app you plan to use before touching the canvas. Each connection uses OAuth — click "Authorize", log into the app, approve permissions. Make stores the token and reuses it across all your scenarios.

Common starting connections for beginners:

  • Google Sheets or Airtable (data destination)
  • Gmail or Outlook (email trigger)
  • Typeform or Jotform (form trigger)
  • Slack or Discord (notification output)

Connect at least two apps before building. Adding connections mid-build disrupts focus and forces you to leave the canvas repeatedly.

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.

A reliable first build: Google Form submission → Google Sheets row.

  1. Click the plus, search "Google Forms", select Watch responses
  2. Choose your connection, pick your form, set the interval to 15 minutes
  3. Click the circle after that module to open the next slot
  4. Search "Google Sheets", select Add a row
  5. Map each form field to the correct column — Make displays the available data from step 1 as clickable variables

Click Run once in the bottom toolbar to test with live data. Make executes the scenario once and shows input and output for every module. Green bubbles mean success; click any bubble to inspect the exact data that flowed through. Do not activate a scenario until at least one test run is completely clean.

Step 4: Use Data Transformation and Filters

The gap between Make and simpler tools opens up here. Between any two modules you can insert logic that would otherwise require code.

Tools modules let you:

  • Format dates into any pattern
  • Convert text to uppercase or lowercase
  • Parse JSON or XML
  • Run basic math on numeric fields
  • Set variables for reuse later in the scenario

Filters add conditional logic between any two modules — a condition that must be true for execution to continue. For example: "Only proceed if the email address contains @company.com." This is an if-statement without writing a single line of code.

Router modules split the flow into parallel branches, each with its own filter. This is the capability where Make most clearly surpasses Zapier — branching in Zapier is more limited and harder to maintain visually as a scenario grows.

Step 5: Schedule and Activate

Scenarios run on a schedule by default. The free plan's minimum interval is 15 minutes; paid plans go as short as 1 minute. Set intervals no shorter than you actually need — the operation cost adds up fast.

For instant response — webhooks, form submissions, new messages — enable instant triggers in the module settings where the app supports them. Instant triggers respond within seconds rather than waiting for the next scheduled poll.

When a test run shows clean results across every module, flip the toggle in the bottom-left from OFF to ON. The scenario is now live.

Common Mistakes That Cost You

  • Skipping the test run. Unmapped fields fail silently. Always click "Run once" before activating — silent errors cause data loss, not visible error messages.
  • No error handler. Add an error route to every scenario so failures send a Slack or email alert. Without one, a broken scenario dies quietly and you may not notice until data is missing or corrupted.
  • Polling every minute without checking the math. At 1-minute intervals, a single trigger module burns through 43,200 operations per month — 43 times the free plan's entire monthly allowance, and enough to exhaust lower-tier paid plans as well.
  • Building complexity before the core flow is stable. Start with two modules and confirm the data moves correctly. Add filters, routers, and transformation steps only after the foundation is verified.

Make vs. Zapier: How to Choose

Choose Make if you need conditional branching, data transformation between steps, or a scenario you expect to grow in complexity. The ~2–3 hour learning investment pays off within the first week.

Choose Zapier if you need something running in 10 minutes and your workflow is a straight line from trigger to a single action. Zapier's library of 6,000+ integrations also matters if you rely on niche apps Make hasn't yet added.

In practice, many small teams run both: Zapier for one-step integrations with uncommon apps, Make for anything that needs reliable multi-step logic and long-term maintainability.

FAQ

Is Make actually free to start? Yes. The free plan includes 1,000 operations per month, two active scenarios, and a 15-minute minimum scheduling interval. That is enough to run several real workflows before deciding whether a paid plan makes sense.

How long does it take to learn Make compared to Zapier? Expect 2–3 hours to get genuinely comfortable. The canvas is intuitive once it clicks, but the first session can feel disorienting. Most beginners find the difficulty lower than expected after completing one working scenario from trigger to output.

Does Make support webhooks? Yes. Make lets you generate a custom webhook URL as a trigger. Any app that can send an HTTP POST request can fire your scenario instantly — no scheduled polling required.

What happens when a scenario fails? Make logs the full input and output for every failed execution so you can pinpoint exactly what broke. If you have added an error handler module, it can notify you via Slack, email, or any connected app. Failed operations do not count against your monthly quota.