How to create your first scenario on Make

beginner 8 min read Updated 2026-03-13

Quick Answer

Sign up at make.com, create a new scenario, add a trigger like Google Sheets Watch New Rows, configure connections, add an action like Send Slack Message, map data, test, and activate with a schedule. Start simple and test thoroughly before going live. Use filters for conditions if needed.

Prerequisites

A free Make.com account
Accounts for apps like Google Sheets, Gmail, or Slack
Basic understanding of app data flow

Step-by-Step Instructions

Sign up or log in to Make

Create a free account at make.com if you don't have one, then log in to access the main Dashboard. This is required before creating scenarios.

Navigate to Scenarios

From the Dashboard, click Scenarios in the left-hand navigation menu. This displays your list of existing scenarios, which will be empty for new users.

Create a new scenario

In the Scenarios page, click the Create a new scenario button in the top-right corner. This opens the Scenario Editor, a blank canvas with a large central + (plus) icon representing the starting trigger module.

Give your scenario a descriptive name for easy management.

Select and add a trigger module

Click the central + icon. A dialog opens listing thousands of supported apps. Search for and select an app, such as Google Sheets > Watch New Rows for monitoring spreadsheet changes or Gmail > Watch Emails for new emails. Use Watch triggers for event-based starts.

Start with simple triggers like Watch New Rows to learn data flow.

Create a connection

In the module configuration panel on the right side, click Add next to Connection. Authorize Make to access your app account, for example sign in to Google for Sheets or Gmail. The default connection name is auto-generated like Google - My Account; everything is done via the UI with no terminal commands needed.

Configure trigger settings

Set parameters in the module panel. For Google Sheets, select Spreadsheet and Sheet from dropdowns with a default limit of 1 new row per run. For Gmail, choose Label (default: Inbox) and Criteria like Newer than 1 day. Click OK to save; uses dropdowns and text fields only.

Keep limits low initially to avoid overwhelming tests.

Add an action module

Click the + icon to the right of the trigger module or hover and select. Search and select an app/action like Slack > Send a Message, Google Sheets > Add a Row, or Email > Send an Email. Connect via existing or new connection.

Map data between modules

In the action module panel, map fields using drag-and-drop from the trigger's output bundle, visible in the left panel after a test. For example, map Prospect Name from Sheets trigger to Slack message body. Defaults use plain text or variables like {{1.Name}} for module 1 output.

Test the trigger first to see available data bundles.

Test the scenario

Click Run once (bottom panel, play icon). If no real data, use Choose where to start and select a bundle from history or manual input. Watch execution bundles flow: green for success, red for error. Debug via the execution log.

Always test with Run once before scheduling.

Schedule and activate

In the bottom panel, set Schedule (default: On-demand; common: Every 15 minutes via Cron */15 * * * *). Toggle Scheduling ON with the slider. Click Save top-left.

Use on-demand first, then add schedules once stable.

Common Issues & Troubleshooting

No data available for mapping in action module

Run the trigger module first with Run once to generate output bundles, then drag from the left panel.

Connection authorization fails

Ensure you have admin access to the app account and re-authorize via the Add button; check app permissions.

Scenario runs but no action triggers

Verify trigger criteria match real data, increase row limits, and check execution log for filtered bundles.

Red error icons during test

Click the red bundle in execution history to view detailed error logs and fix mappings or connections.

Only one trigger per scenario

Create separate scenarios for multiple independent triggers; use routers for conditional branches within one.

Visit Make View Make Pricing