Make (Integromat) Setup: Your First Automation Without the Confusion

Step 1: Account Creation and Free Tier Limits (5 minutes)

1. Sign up at make.com. Email or Google SSO. No credit card required for the free plan.
2. Skip the onboarding wizard. Make shows you a guided tour with sample scenarios. Skip it — we'll build something real instead.
3. Understand your free tier limits:
   • 1,000 operations per month. An “operation” is any module that processes data. More on this below.
   • 2 active scenarios. You can build more, but only 2 can be turned on at once.
   • Minimum 15-minute scheduling interval. Scenarios check for new data every 15 minutes at fastest.
   • 10 MB data transfer limit. Fine for text data. Can be tight for file attachments.

Step 2: Understanding Scenarios, Modules, and Operations (10 minutes reading)

Make uses different terminology than Zapier. Understanding these three concepts upfront prevents confusion for the entire time you use the platform.

The visual builder is Make's core advantage.Unlike Zapier's linear step list, Make shows your automation as a flowchart. You drag modules onto a canvas, draw connections between them, and can see the entire flow at a glance. This makes complex automations (routers, error handlers, loops) manageable instead of confusing.

Step 3: Build Your First Scenario Step by Step (15 minutes)

We'll build a practical automation: when a new row is added to a Google Sheet, create a contact in your CRM (HubSpot, Pipedrive, or any CRM Make supports). This is a pattern that works for lead capture, form responses, or manual data entry.

1. Click “Create a new scenario.”You'll see an empty canvas with a single empty circle (the starting module).
2. Click the empty circle and search for “Google Sheets.”Select “Watch New Rows.” This is your trigger — it checks for new rows at your set interval.
3. Connect your Google account.Click “Create a connection” and authorize Make via Google OAuth. Select the specific spreadsheet and sheet tab.
4. Set “Limit” to 10. This means each run processes up to 10 new rows. On the free plan, processing 10 rows = 10 operations from this module alone, so be mindful.
5. Click the right side of the Google Sheets moduleto add the next module. A “+” button appears. Click it and search for your CRM (e.g., “HubSpot”).
6. Select “Create a Contact” (or “Create a Person” for Pipedrive). Connect your CRM account.
7. Map the fields.Click each CRM field and select the corresponding Google Sheets column from the dropdown. Email → Column A (or whatever your email column is). First Name → Column B. And so on.
8. Click “Run once”at the bottom left. Make will process any new rows currently in your sheet. A green checkmark on each module means success. A red X means something went wrong — click the module to see the error.
9. Check your CRM. Verify the contact was created with the correct data.
10. Turn on scheduling(Step 5 below) once you've confirmed it works.

Step 4: Error Handling Basics (10 minutes)

This is the section that separates Make from Zapier. Zapier hides errors in a task history log that most people never check. Make forces you to decide what happens when something breaks — and that's genuinely better for production automations.

How Make Handles Errors

When a module fails (API timeout, invalid data, rate limit), Make can do one of five things. Right-click any module and select “Add error handler” to configure:

Set Up Error Handling for Your First Scenario

1. Right-click the CRM module → “Add error handler.”
2. Add a “Break” handler. This is the safest default. If the CRM API fails (timeout, duplicate contact), the failed row goes into a retry queue instead of being lost.
3. Set retry attempts to 3 with increasing delays. Break handlers retry automatically at intervals you set.
4. Optionally add a notification module on the error path. Connect an “Email” or “Slack” module after the error handler to notify yourself when something fails. This uses 1 extra operation per error but prevents silent failures.

Step 5: Scheduling and Execution Monitoring (10 minutes)

Turn On Scheduling

1. Click the clock icon at the bottom of your scenario canvas.
2. Set the interval. Free plan minimum is 15 minutes. For a Google Sheets → CRM scenario, 15 minutes is fine. New rows don't need instant processing.
3. Toggle the scenario ON using the switch at the bottom left of the canvas. The scenario is now active and will run every 15 minutes.

Monitor Executions

1. Go to the scenario page → “History” tab. This shows every execution with status (success, warning, error), operation count, and processing time.
2. Click any execution to see the data flow. Make shows you the exact data that passed through each module. This is invaluable for debugging — you see what went in and what came out at every step.
3. Set up execution notifications. Scenario settings → Notifications. Enable “Errors” to get emailed when a scenario fails. Skip “Warnings” unless you want high-frequency alerts.
4. Check operation usage. Dashboard → Usage. Track your monthly operation consumption. Free tier is 1,000/month — monitor weekly to avoid surprises.

When to Move from Free to Core

The free-to-Core upgrade is one of the best values in SaaS.$10.59/month for 10,000 operations, unlimited scenarios, 1-minute intervals, and data stores. Compare that to Zapier Professional at $29.99/month for 750 tasks with single-step still counting. Make's Core plan costs less and does more.

Common Setup Mistakes

• Not understanding operation counting.A scenario with 5 modules that processes 10 items uses 50 operations (5 modules × 10 items). On the free plan, that's 5% of your monthly limit in one run. Set low limits on trigger modules (5–10 items per run) until you understand your consumption.
• Skipping error handlers.Make lets you build scenarios without error handling. Don't. Add at least a “Break” handler on every action module. Silent failures accumulate and create data gaps you won't notice for weeks.
• Using “Run once” to test with live data.“Run once” processes real data. If your scenario creates contacts or sends emails, the test creates real contacts and sends real emails. Use test/sandbox accounts for initial testing, or at least verify the output module is pointed at the right place.
• Building complex scenarios before understanding bundles.Bundles are Make's superpower and its biggest gotcha. If a trigger returns 5 items, every downstream module runs 5 times. If you have a router that splits into 2 paths with 3 modules each, that's 5 × 6 = 30 operations. Understand bundle flow before building multi-path scenarios.
• Connecting too many apps at once.Each app connection uses OAuth tokens that can expire. Start with 2–3 app connections. Add more as you build scenarios that need them. Unused connections create maintenance overhead (token refresh failures).

What to Skip on Day 1

• Custom functions. Make lets you write JavaScript transformations inside modules. Powerful but unnecessary for your first scenarios. Use built-in functions (text replace, date format, math) instead.
• Data stores. Make's built-in key-value database is useful for deduplication and tracking state between runs. But it adds complexity. Use a Google Sheet as your “database” for the first month — it's easier to inspect and debug.
• Complex routers. Routers split scenarios into branches. Start with linear scenarios (trigger → action → action). Add branching when you have a specific condition that requires different outputs.
• Webhooks. Custom webhooks are how you connect apps that don't have native Make modules. But they require understanding HTTP methods, headers, and JSON parsing. Stick to built-in modules first.
• Templates marketplace. Make has a templates library. Most templates are over-engineered for simple use cases. Build from scratch so you understand every module in your scenario.