Make.com Tutorial: Build Your First Automation Scenario Step by Step

Disclosure: We may earn a commission when you purchase through links on this site, at no extra cost to you. How we make money.

Make.com (formerly Integromat) has a reputation for being powerful but intimidating. That reputation isn’t entirely undeserved — the visual canvas, the modules, the bundle concept — it’s a different mental model than Zapier’s step-by-step list. But once you understand how it thinks, building in Make is often faster and more flexible for anything beyond simple two-step automations. This make.com tutorial starts from zero: no assumed knowledge, no jargon shortcuts, just a clear walkthrough from an empty canvas to a working scenario.

We’ll build a practical example: when a new form submission arrives, save it to a Google Sheet and send a notification email. Simple enough to follow, useful enough to actually deploy.

Understanding the Make.com Mental Model

Before touching the canvas, three concepts to internalize:

• Scenarios: What Zapier calls a Zap, Make calls a Scenario. It’s your automation — a connected flow of modules.
• Modules: Each step is a module. Modules receive data, do something with it, and pass the result to the next module. The trigger module starts everything; action modules do work.
• Bundles: When a trigger fires, it produces a “bundle” of data — one set of values for each item it found. If a trigger checks for new form submissions and finds three, it produces three bundles, and your scenario processes each one in turn. This matters when you’re working with multiple records.

The visual canvas shows modules as circles connected by lines, flowing left to right. This makes the data flow much easier to see than a vertical list, especially once you add branching logic.

Step 1: Create a New Scenario

Log in to Make.com. From the left sidebar, click Scenarios, then Create a new scenario. You’ll see a blank canvas with a large plus button in the center. Click it to add your first module — the trigger.

For our example, choose Google Forms (or whatever form tool you use — Typeform, Tally, and most major form builders are available). Select the trigger event — typically Watch Responses or New Response. Connect your Google account when prompted, then select the specific form you want to monitor.

Click OK to save the module. You’ll now see it as a circle on the canvas.

Step 2: Add a Google Sheets Module

Click the small arrow coming out of the right side of the trigger module to add the next step. Search for Google Sheets and choose the Add a Row action. Connect your Google account, select the spreadsheet and sheet tab you want to write to, and then map the fields.

This is where Make’s interface differs from Zapier. Instead of dropdowns, you’ll see column labels and blank fields next to them. Click inside a field and a panel opens showing the data available from the trigger — form field names from your submission. Click to insert them into the appropriate columns.

Save the module. Now the canvas shows two connected circles: the form trigger flowing into the Sheets action.

Step 3: Add an Email Notification Module

Click the arrow off the Sheets module to add a third step. Search for Email and choose Send an Email (Make’s built-in email sender, no additional connection needed). Fill in the To, Subject, and Content fields, using trigger data where needed — for example, including the submitter’s name and email from the form in the notification body.

At this point your scenario has three modules connected in sequence: form response → Google Sheet row → email notification.

Step 4: Test the Scenario

Before turning it on, test it. In the bottom toolbar, click Run Once. Make will execute the scenario one time using the most recent data from your trigger source. You’ll see colored circles and counters on each module showing how many bundles were processed and whether each step succeeded.

Click on any module’s counter bubble to inspect exactly what data flowed through it — inputs in, outputs out. If something fails, the error message appears here with enough detail to diagnose the issue.

Check your Google Sheet and your email inbox to confirm the test data arrived correctly.

Step 5: Set the Schedule and Activate

Unlike Zapier (which can use instant triggers), most Make scenarios run on a polling schedule — checking for new data every X minutes. Click the clock icon in the bottom-left of the canvas to set the interval. For most business workflows, every 15 minutes is sufficient. If you need faster response, every 5 minutes is available on paid plans; instant triggering is possible with webhook-based triggers.

Once the schedule is set, toggle the scenario ON in the top-right corner. It’s now running automatically.

Common Beginner Mistakes to Avoid

• Forgetting to save modules: Each module needs you to click OK before the connection is saved. If you click away without saving, your configuration is lost.
• Not testing before activating: Run Once with real data before turning a scenario on. Discovering an error after it’s been live (and potentially creating duplicate records or sending wrong emails) is more painful than a 5-minute test.
• Misunderstanding operations vs. tasks: Make prices on operations — each module execution counts. A three-module scenario processing 100 bundles uses 300 operations. Keep this in mind if you’re watching costs.
• Using the wrong trigger type: “Watch” triggers in Make check for new items since the last run. Make sure to set the limit appropriately (how many items to process per run) so you don’t flood a new scenario with months of historical data on the first execution.

Where to Go From Here

Once your first scenario is working, the most useful next features to explore are:

• Routers: Split one trigger into multiple parallel paths based on conditions — similar to Zapier’s Paths but with more flexibility
• Aggregators and Iterators: Handle arrays of data (like processing each line item in an order separately)
• Error handlers: Set up what happens when a module fails, rather than letting the scenario stop silently

The visual canvas is Make’s real advantage — once you have three or four modules, being able to see the whole flow at once is genuinely easier than scrolling through a vertical list. Build the simple scenario first, get comfortable with the interface, and then start exploring the more powerful features as your needs grow.