Builder · Level 2 of 3
Make’s blank canvas is the biggest thing standing between you and your first automation: a grid of nothing, a search bar for "apps," and no obvious starting point. This walks you through building one real scenario end to end: a Google Form that lands in a Google Sheet, and a Make scenario that watches that sheet and posts a Slack message the moment a new row appears. By the end you’ll have a working automation and a clear sense of how far Make’s free plan will actually take you before you need to pay for more operations.
Some links below are affiliate links. If you sign up through them, Automate My Life may earn a commission at no extra cost to you, which helps keep the site free. Only genuinely useful tools receive a recommendation.
What Is Make, and When Should You Use It Instead of Zapier or n8n?
Make is a visual automation platform: you drag modules onto a canvas, connect them with lines, and each module does one job: watch a spreadsheet, send a Slack message, create a calendar event. It reads more like a flowchart than a form, which is exactly what trips people up coming from Zapier’s linear, step-by-step builder. The payoff is flexibility: Make lets you branch, loop, and route data in ways a straight-line builder doesn’t make obvious, without touching n8n’s self-hosted setup and workflow-as-code approach.
Reach for Make specifically when your automation needs more than one path, when you want a visual map of the whole workflow at a glance, or when you’re comparing platforms and want the middle ground between Zapier’s simplicity and n8n’s technical depth. If you haven’t picked a platform yet, the full breakdown of how these three differ in practice (pricing, learning curve, and where each one falls apart) is in Zapier vs Make vs n8n in 2026: The Honest Comparison. This post assumes you’ve already landed on Make and want the thing built.
Setting Up Your Make Account and Understanding the Free Plan
Make’s free plan costs nothing and doesn’t expire, which makes it the right place to build and test your first scenario before deciding whether you need more. Create a free Make account using the email you want tied to your automations. You can add a team or move to a paid plan later without losing anything you’ve built.
Every plan runs on operations, which Make now calls credits. Each time a module in your scenario actually fires (checks for a new row, sends a message, transforms a field), it uses roughly one credit. The free plan currently includes 1,000 credits a month, resetting on your billing date with no rollover. That sounds generous until a scenario checking for new form submissions every few minutes racks up credits just by checking, whether or not anything new showed up. The operations math further down covers how to keep that number under control.
Before you build anything, get the other two pieces in place: a Google account with access to Forms and Sheets, and a Slack workspace where you have permission to post messages. A free Slack workspace works fine for testing, and both are free to create if you don’t already have them.
Building Your First Scenario: Google Form to Sheets to Slack
The scenario you’re building has three pieces, but only two of them live inside Make. Google Forms writes directly to a linked Google Sheet on its own. No automation is needed for that part. Make’s job starts where the spreadsheet gets a new row: it watches that sheet, then tells Slack about it.
Step 1: Create the Form and Link It to a Sheet
- In Google Forms, build a short form: a name field, an email field, and one question is enough for a test run.
- Open the form’s Responses tab and click the green Sheets icon to create a linked spreadsheet. Every submission now lands there automatically as a new row.
- Submit one test response yourself so the sheet has a header row and at least one data row before you connect Make. The row-watching module needs an existing structure to read.
Step 2: Watch the Sheet From Make
- From your Make dashboard, click Create a new scenario and search for the Google Sheets app in the module picker.
- Choose the Watch New Rows module. Connect your Google account when prompted and grant Sheets access.
- Select the spreadsheet the form created, then the specific tab inside it. Set the module to start from now so it doesn’t try to process every old test row on its first run.
- Click the module’s Run once button and submit a fresh test form response. The new row should appear in Make’s output bundle within a few seconds. That confirms the connection before you add anything downstream.
Step 3: Add the Slack Notification
- Click the plus icon to the right of the Google Sheets module and search for Slack.
- Choose Create a Message, connect your Slack workspace, and authorize Make when Slack asks for permission.
- Pick the channel that should get the alert, then build the message text using the fields Make pulled from the sheet: select the name, email, and response fields from the list Make offers instead of typing them by hand, so the message updates automatically with each new submission.
- Save the scenario, click Run once again, and submit one more test form response. If the Slack message shows up with the right data filled in, both modules are wired correctly.
Turn the scenario on with the toggle in the top-left corner, then set its schedule. Make shows you the polling intervals your plan allows when you click the clock icon on the trigger module. Shorter intervals mean faster Slack alerts, but they also mean more scheduled checks against your credit budget, even on runs where nobody submitted the form.
How Do You Test and Troubleshoot a New Scenario?
Every module has a Run once option, and it’s the fastest way to isolate a problem: run the Google Sheets module by itself first, confirm it’s pulling the row you expect, then add Slack and run the whole scenario together. If a run fails, Make’s execution history shows exactly which module errored and the raw data it was working with, which is usually enough to spot a missing field or a permission that wasn’t granted.
The common first-timer snags: forgetting to submit a test row before connecting the Sheets module, so it has nothing to watch; mapping a field that no longer matches because the form question wording changed after the sheet was created; and leaving the scenario’s schedule off entirely. A built scenario does nothing until you flip it on.
How Do You Make Your Free Plan’s Operations Last?
A two-module scenario like this one uses roughly two credits per run where both modules fire, plus a smaller check-in cost on cycles where the Sheets module polls and finds nothing new. Run that schedule every few minutes, all day, and the checking itself becomes the bulk of your usage, not the actual notifications. The free plan’s 1,000 monthly credits go further with a few adjustments:
- Widen the polling interval for anything that isn’t time-sensitive. A form that gets a handful of submissions a day doesn’t need a check-in every few minutes.
- Turn a scenario off, not just pause the schedule, when you’re done testing it, so leftover test runs don’t quietly use credits overnight.
- Check your usage under the account’s operations dashboard before building a second or third scenario, so you know how much headroom is actually left.
If you outgrow the free tier, the paid plans scale by credit volume rather than by feature: Core starts around $12/month, Pro (the plan Make positions as its default recommendation) around $21/month, and Teams around $38/month, each billed on the credits included at that tier. Check Make’s current pricing page before committing, since these numbers move.
Pricing and credit figures above come from Make’s own pricing and help-center pages, checked August 2026. Make updates plan details periodically, so confirm current numbers on Make’s pricing page before committing to a paid tier.
Where This Breaks, and What It Costs You in Upkeep
A two-module scenario is about as low-maintenance as Make gets, but it’s not maintenance-free. The most common failure is a broken connection: if you change your Google password, get removed from the Slack workspace, or an admin revokes app access during a security review, the scenario stops silently until you reconnect the account from inside Make. Renaming the sheet’s tab or moving the linked spreadsheet to a different Google Drive folder also breaks the Watch New Rows module’s reference, and you’ll need to re-select the sheet rather than just rename it back.
On the privacy side, connecting Google Sheets and Slack to Make means Make holds a standing connection with read access to that spreadsheet and post access to the Slack channel you chose, not just the one-time permission grant it feels like during setup. Scope the connection to what the scenario actually needs (a single sheet rather than your whole Drive, where the app’s permission model allows it), and if you stop using a scenario, turn it off and remove the connection from Make’s account settings rather than leaving an unused integration with standing access to your data.
Set a calendar reminder to glance at the scenario’s execution history every month or two while you’re still learning Make. Silent failures are the main risk with any “invisible” automation. The form still collects responses, but nobody in Slack knows a new one arrived, and you won’t notice until someone asks why they weren’t pinged.
What Should You Build Next?
This scenario is deliberately small so the mechanics stick: trigger, map data, send message, test, turn on. Once it’s running, the same three-module shape extends to plenty of other Builder-tier automations: new sheet rows that create calendar events, new form entries that also fire an email, or a second Slack channel that only gets flagged responses. If Make ends up feeling like more platform than you need, or you want to see how it stacks up against the alternatives before going further, Best Zapier Alternatives in 2026 (Free and Paid) covers where Make fits against the rest of the field.