Make Tutorial (2026): Build Your First Scenario Step by Step
komasu Tools is supported by readers like you. We may earn an affiliate commission when you purchase through our links, which enables us to offer our research for free. How we make money
A working Make scenario that posts a formatted Slack message to a channel every time a new row is added to a Google Sheets spreadsheet.
Try Make for freeWhat you will build
In this tutorial you will build a scenario, which is Make's name for an automated workflow. It watches a Google Sheets spreadsheet for new rows and posts a formatted message to a Slack channel for each one.
The example is a simple sales alert. Every time someone adds a new prospect to a spreadsheet called "Prospects", your team gets a Slack message in the "sales-team" channel with the name, email, country and details. This mirrors the Get started guide in Make's own help center, so every screen and button name you see here comes from Make's documentation.
The scenario has two modules. A module is one step in one app. The first is the trigger "Watch New Rows" in Google Sheets, and the second is the action "Send a Message" in Slack. At the end you will also add a filter so only some rows trigger a message.
If you have not decided whether Make is right for you, read our Make review first. Otherwise, open a Make account in another tab.
Before you start
You need three accounts, according to Make's guide:
- A Make account. The Free plan is enough for this tutorial.
- A Google account with access to Google Sheets.
- A Slack account and a workspace where you can create a channel.
Then prepare your apps:
- In Slack, create a public channel named "sales-team".
- In Google Sheets, create a spreadsheet named "Prospects".
- In the first row, add these column headers: First Name, Last Name, Country, Email, Phone Number, Details.
- Add one row of sample data under the headers.
Two terms will help you follow along. An operation is a single module run that processes data or checks for new data. A bundle is one item of data passing through the scenario, such as one spreadsheet row. Make bills in credits, and by default one operation uses one credit.
Step 1: Create a new scenario
Log in to Make and click + Create a new scenario in the top-right corner. You can also find this button in the Scenarios tab in the left sidebar. This opens the Scenario Builder, the canvas where you build your workflow.
Click New scenario in the top-left corner and type a name, such as "New prospect notification". Then click the save icon in the Scenario Builder toolbar. Saving early is a good habit, because the toolbar save is the only way to store the whole scenario.
Step 2: Add the Google Sheets trigger
Click the large plus in the center of the canvas. A list of apps opens. Type "Google Sheets" in the search bar and select it. If you pick the wrong app, click Back to return to the list.
From the Google Sheets modules, choose Watch New Rows. This is a trigger, the module that starts the scenario. It is a polling trigger, which means it checks the sheet for new rows each time the scenario runs rather than reacting instantly.
Step 3: Connect your Google account
Make needs permission to read your spreadsheet. In the module settings, click Create a connection. Give the connection a name, such as "My Google connection", and click Sign in with Google.
Google asks you to pick an account and select what Make can access. Choose the account that owns the "Prospects" spreadsheet, select the access options and click Continue. You only need to do this once, and later scenarios can reuse the same connection.
Step 4: Set up the trigger
Now tell the module which sheet to watch. Make's guide uses these settings:
| Field | Value |
|---|---|
| Search Method | Leave the default, "Search by path" |
| Drive | Select your drive from the dropdown |
| Spreadsheet ID | Click "Click here to choose file" and pick "Prospects" |
| Sheet Name | Sheet1 |
| Table contains headers | Yes |
| Row with headers | Leave the default, A1:Z1 |
| Limit | 20 |
Setting Table contains headers to Yes is important. It tells Make to use your column names, such as "First Name", as the labels for each value. Without it, values are labeled A, B, C and so on. The Limit sets how many new rows are processed in one run.
Click Save to store the module settings. A Choose where to start dialog appears. Select All, so the module processes the rows already in the sheet first and then new rows as they are added. If you close this dialog by mistake, right-click the Google Sheets module and choose "Choose where to start".
Step 5: Test the trigger
Before adding Slack, check that Make can read your sheet. Right-click the Watch New Rows module and select Run this module. When the run finishes, an output bubble appears above the module.
Click the bubble to see the data. You should see your sample row, with each value labeled by its column name. Compare it with your spreadsheet to confirm it is correct. Make's help center notes that each test run of this module uses one credit.
Step 6: Add the Slack module
Hover over the right side of the Google Sheets module and click the + icon, or right-click the module and choose Add a module. Search for "Slack", select it, and choose Send a Message.
Click Create a connection, choose the connection type Slack (user), and click Save. Slack asks you to authorize Make, so click Allow. Make's Slack documentation also lists a Slack (bot) connection; if you use one, the bot must be a member of the channel, or the module fails with a "Channel Not Found" error.
Step 7: Map the row data into the message
Mapping means taking output from one module and using it as input for the next. This is the core skill in Make.
First choose where the message goes. Set Enter a channel ID or name to "Select from the list", Channel type to "Public channel", and then pick "sales-team" as the channel.
Now click the Text field. A mapping panel opens with the output of "Google Sheets > Watch New Rows". Type your message and click values in the panel to insert them, or drag them into place. A clear format looks like this:
New prospect added! Name: First Name Last Name Email: Email Country: Country Phone: Phone Number Details: Details
Each item in italics is a mapped value from the panel, not typed text. Put a space between First Name and Last Name, or the two values run together. Click Save in the module, then the save icon in the toolbar.
Step 8: Test the whole scenario
Click Run once in the Scenario Builder toolbar. Make runs both modules, and a bubble appears above each one. The number in each bubble shows how many operations ran.
Open the Slack channel and check that the message arrived with the right values. Then click the bubble above the Slack module to see exactly what Make sent. If a field is empty, go back to Step 7 and check that you mapped the value rather than typing its name.
Watch the credit math here. The trigger uses one operation per check however many rows it returns, while the Slack module runs once per bundle. So if the trigger finds 10 new rows, the run costs 11 operations.
Step 9: Add a filter (optional)
A filter sits on the link between two modules and only lets bundles through when a condition is true. Suppose your US team only wants US prospects.
Click the wrench icon on the line between the two modules and choose Set up a filter. Enter a Label such as "US prospects only". Click the Condition field and map the "Country" value from Google Sheets. Leave the operator under Text Operators set to Equal to, and type "USA" in the field below. Click Save, then save the scenario.
Run the scenario again with one US row and one non-US row. Only the US row should reach Slack.
Step 10: Schedule and activate the scenario
A scenario only runs automatically once you schedule and activate it. In the toolbar, click the schedule setting, which shows "Every 15 minutes" by default. This opens the Schedule setting window.
Make offers options such as "At regular intervals", "Daily", "Weekdays (Mon-Fri)", "Weekly", "Monthly", "Specified dates" and "On demand". Keep "At regular intervals" with a 15-minute interval, which is also the minimum on the Free plan. Click Save, then confirm Activate scenario.
From now on, Make checks the sheet every 15 minutes and posts one Slack message per new row.
Open Make and build this scenario
Common mistakes
- Leaving blank rows in the sheet. Make's documentation warns that if a sheet contains a blank row, Make does not process the rows after it. Add new rows directly under existing data.
- Forgetting to save the scenario. The Save button in a module only stores that module. Use the save icon in the toolbar to store the whole scenario.
- Typing field names instead of mapping them. Typed text is sent as is. Values must be clicked or dragged from the mapping panel.
- Choosing the wrong starting point. If you skip "Choose where to start", the trigger may not process the rows you expect. Right-click the module to set it again.
- Using a bot that is not in the channel. A Slack (bot) connection fails if the bot has not been added to the channel.
- Expecting instant messages. Watch New Rows is a polling trigger, so messages arrive on the next scheduled run, not the moment you type.
- Burning credits on tests. Every test run uses credits. Use a small sample sheet while you build.
Next steps
You now know the core loop in Make: trigger, connection, mapping, test, schedule. Most scenarios are variations of these steps.
Good next projects are adding a router to send different countries to different channels, or replacing Slack with an email module such as Gmail to send a summary. Make's help center and Make Academy both have free follow-up lessons on routers and aggregators.
If you are still choosing a tool, compare Make with its closest rival in Make vs Zapier, or see how a self-hosted tool handles the same idea in our n8n tutorial. For the full picture, see the best automation tools ranking.
Frequently asked questions
Can I build this scenario on Make's Free plan?
Yes. The Free plan includes 1,000 credits per month, which is plenty for this scenario. Scheduled runs on the Free plan can happen at most every 15 minutes.
How many credits does this scenario use?
The Google Sheets trigger uses one operation per check, and the Slack module uses one operation per new row. By default one operation equals one credit, so ten new rows in one run cost about 11 credits.
Why does the scenario not post right away when I add a row?
Watch New Rows is a polling trigger. It only checks for new rows when the scenario runs on its schedule, so a new row is picked up on the next scheduled run.
Does testing the scenario use credits?
Yes. Make's help center notes that each test run of the Watch New Rows module consumes a credit, and Run once uses credits like a normal run.
Can I send an email instead of a Slack message?
Yes. Replace the Slack module with an email module, such as the Gmail app, and map the same row values into the subject and body fields.
Why are some new rows skipped?
Make's documentation warns that if a sheet contains a blank row, Make does not process the rows after it. Keep new rows directly below the existing data.
See the update history of this article
- First published.