Make.com Tutorial for Beginners (2026): Your First Scenario

Short answer: sign up for Make's Free plan, which includes 1,000 credits a month ^[6]. Build a scenario with one trigger and one action, run it once to test, then set a schedule. Make counts each module run as an operation, and most operations use 1 credit ^[4], so a two-module scenario that runs a few hundred times a month fits on Free.

Quick answer

A Make automation is called a scenario. You build it by linking modules, starting with a trigger that watches an app for new data ^[2]. This guide walks through Make's own first-scenario setup (Google Sheets to Slack) ^[1], then two small examples you can copy: an order alert for a store and a form-to-email flow for creators.

What you need

• A Make account. The Free plan costs nothing ^[6].
• Accounts for the apps you want to connect. Make's walkthrough uses a Google account and a Slack workspace, both free to create ^[1].
• About 20 minutes and a test spreadsheet you don't mind filling with fake rows.

Key terms: scenarios, modules, triggers

• Scenario: a series of modules that move and transform data between apps. Each team can create up to 100 scenarios a day, and each scenario can be up to 2 MB ^[1].
• Module: one building block that does one job, such as watching a sheet or sending a message ^[2]. Make has four kinds: triggers, searches, actions and universal modules.
• Trigger: the first module. It picks up new data, and you can add only one per scenario ^[2]. Polling triggers (often named "Watch...") check for new data on your schedule. Instant triggers are webhooks: the app tells Make the moment something happens, and they show a lightning icon ^[2].
• Actions and searches: actions create, update, get or delete records; searches find records. You can add as many as you need ^[2].
• Bundle: one unit of data, like a single row, email or order ^[3].

Build your first scenario

Make's help center uses this example: when someone adds a prospect to a Google Sheet, send a Slack message to the sales team ^[1]. The same steps work for any trigger and action.

1. Create a new scenario in the Scenario Builder.
2. Add the trigger. Pick the "Google Sheets > Watch New Rows" module. Make asks you to create a connection to your Google account; app modules need one before they work ^[2].
3. Choose where to start. Right-click the trigger and pick a starting point, such as "The current moment" or a specific record. This applies only to the first run ^[2].
4. Add the action. Add a Slack module that sends a message, connect Slack, and map fields from the sheet (name, email) into the message text.
5. Test it. Add a row to the sheet and click "Run once". The bubble above each module shows its operation count, and you can toggle on the credit count next to the scenario name ^[3].
6. Save and activate. Click "Save", set the timing in "Schedule settings" (next section), then click "Activate scenario" so it runs without you. Check past runs in the "History" tab ^[5].

How credits work

An operation is one module run that processes or checks data. Most modules run once per bundle, so sending 5 emails is 5 operations. Triggers are the exception: they run once per check, however many bundles they return ^[3]. For non-AI apps, 1 operation equals 1 credit ^[4].

Make's own example: a trigger returns 10 new form responses, and three later modules each run 10 times, for 31 operations in one run ^[3]. Adding an aggregator so one email lists all 10 contacts cut a similar scenario from 11 operations to 3 ^[3]. AI features can use more: Make's AI Provider and some built-in AI apps charge credits based on tokens ^[4].

Scheduling your scenario

By default, a scenario runs every 15 minutes. Open "Schedule settings" in the scenario toolbar (it shows "Every 15 minutes" by default) to change it ^[5]. You can choose regular intervals, once, daily, weekdays, weekly, monthly, specified dates or on demand, and a daily schedule can hold several run times ^[5]. The shortest interval depends on your plan; on Free it is 15 minutes ^[6]. Make supports instant (webhook) triggers, which set the scenario to "Immediately as data arrives" ^[2].

Store example: new order alert

Say your orders land in a Google Sheet. Trigger: Google Sheets "Watch New Rows". Action: Slack or Gmail message with the order number, product and total. Schedule: three times a day. Our estimate: that's about 90 checks a month. At 300 orders a month, the action adds about 300 operations, so the total stays near 390 credits, inside Free. For Shopify-specific scenarios, see Make.com Shopify integration: 7 automations.

Creator example: form to sheet and email

For a lead magnet or a coaching inquiry form: trigger on new Google Forms responses, add a Google Sheets "Add a Row" action, then a Gmail "Send an Email" action with the download link. Each response costs 2 operations plus the trigger check ^[3]. Our estimate: with 200 responses and an hourly schedule, expect about 400 action operations plus about 720 checks, which is over 1,000. Switching to four runs a day cuts the checks to about 120.

If the form is there to sell something, a funnel builder handles the page, the form and the emails in one place. Our ClickFunnels vs Systeme.io comparison shows what each costs.

When the Free plan runs out

When credits run out, scenarios stop until the next cycle unless you buy more ^[6]. Paid plans are priced by credits, set with a slider. At 10,000 credits a month, Nina's Oct 19 browser check found ^[6]:

Prices rise with the credit slider. To compare Make with Zapier on cost, read Make vs Zapier pricing.

Want the cost side in more depth? Make credits explained works through what each run uses, and n8n vs Make compares Make with a tool that bills per run.

Beginner mistakes to avoid

• Leaving the 15-minute default on a polling trigger on Free; the checks alone can use your credits.
• Sending one email per row when one summary would do. An aggregator reduces operations ^[3].
• Testing Delete modules on real data. Some services can't recover items deleted through the API ^[2].
• Huge searches. Most searches return up to 3,200 objects or 5 MB per run ^[2].

FAQ

Is Make really free?

Yes, the Free plan costs $0 and includes 1,000 credits a month ^[6]. Heavier use needs a paid plan or extra credits.

How do I use Make?

Create a scenario, add a trigger, add one or more actions, run it once to test, then set a schedule ^{[1] [5]}.

What is the difference between operations and credits?

Operations count module runs; credits are what you pay with. For most apps they are 1 to 1, while AI features can use more ^[4].

Can I self-host Make?

No. Make is cloud-only; its on-prem agent connects to local systems but isn't self-hosting ^[6].

Bottom line

Start small: one trigger, one action, a test run and a modest schedule. Watch the credit count in the first week, then decide whether you need a paid plan. You can start on Make's Free plan today.

We earn a commission on Make links.