Your First Make.com Scenario, Step by Step (With Credit Costs)

Your first Make scenario takes about thirty minutes — a little longer than the Zapier equivalent, because Make gives you a visual canvas instead of a list. That canvas is also why it’s cheaper to run: every circle you place on it is one credit per execution, and you can see your bill taking shape as you build.

This walkthrough builds a real automation end to end and keeps the credit meter visible throughout, so you finish understanding both the builder and the thing that actually decides your monthly cost.

How Does Make Differ From Zapier?

Make gives you a canvas where you place modules and connect them; Zapier gives you a vertical list of steps. The visual difference is obvious in ten seconds. The billing difference matters more and takes longer to notice.

That last comparison is worth sitting with. Zapier’s free plan lets you react instantly but only with two steps. Make’s free plan lets you build as complex a scenario as you like but makes you wait up to 15 minutes for it to run.

What Will You Build?

A form submission that lands in a spreadsheet and sends a notification — the same automation as the Zapier walkthrough, so you can compare the two directly. Four modules total.

Filters are free and they stop the run. Placing one at module two means every filtered-out submission costs you one credit instead of three. Over a year of spam entries, that adds up.

How Do You Build It, Step by Step?

Six stages on the canvas. Make lets you run a scenario manually at any point, so test as you go rather than at the end — the visual data inspector is the whole reason to use this tool.

1. Create a scenario and add the trigger. From your dashboard, create a new scenario. Click the large plus, search for your form tool, and choose the “watch” trigger — usually “Watch Responses” or “Watch New Submissions”.

2. Connect the account and set the trigger. Add a connection and authorise access. Then set how many records the trigger should fetch per run. Set this to a small number while testing, because this is the setting that controls the multiplication.

3. Run once to fetch real data. Click “Run once”, then submit a test entry in your form. Make pulls the record and shows it in a data inspector bubble above the module. Open it and look at the field names — you need them next.

4. Add a filter. Click the connector line after the trigger and add a filter. Set a condition that excludes what you don’t want — for example, email address does not contain your own domain. Name the filter something readable.

5. Add the spreadsheet module. Click the plus after the filter, choose Google Sheets, then “Add a Row”. Select the spreadsheet and sheet, then map each column by clicking the field and picking the matching value from the trigger data panel.

6. Add the notification module and schedule it. Add your notification app and compose the message, inserting trigger fields where you want submitted values. Then set the schedule — how often the scenario checks. Save and switch it on.

Run it once more end to end, then submit a genuinely real entry and watch it flow. The canvas animates each module as data passes through, which makes it obvious where something stalls.

How Do Credits Actually Get Consumed?

One credit per module run — with the trigger metered differently from everything else. Make’s documentation defines an operation as “a single module run to process data or check for new data,” and the trigger “only run[s] once to check for or retrieve data, regardless of the number of bundles returned.”

Then the multiplication starts. Every module after the trigger runs once per record returned, because “modules process each bundle separately, meaning each bundle triggers its own module run.”

This is why the trigger’s record-limit setting matters so much. A scenario that runs every 15 minutes and fetches up to 50 records behaves completely differently from one fetching 1. Full breakdown in our Make pricing guide.

What Does It Cost to Run?

Three credits per submission on this build, so around 600 credits at 200 submissions a month — well inside the $9 Core plan’s 10,000. The free plan’s credit allowance would cover it too, but its interval limit probably won’t work for you.

For a lead notification, a 15-minute delay is the difference between reaching someone while they’re still on your site and reaching them after they’ve contacted a competitor. That single limitation is what moves most people to Core.

What Should You Add Before Trusting It?

An error handler and a sensible name. Both take minutes and both prevent the failure mode where a scenario stops working and nobody notices for a month.

What Goes Wrong on a First Scenario?

Four things, all visible on the canvas once you know where to look.

Frequently Asked Questions

How do I create my first Make scenario?

Create a scenario, add a trigger module and connect the app, run once to fetch real data, add a filter, add your action modules and map the fields, then set the schedule and switch it on. About thirty minutes for a four-module build.

What counts as a credit in Make?

One module run. Make defines an operation as “a single module run to process data or check for new data.” The trigger costs one credit per check regardless of records returned; every module after it runs once per record.

Is Make free to use?

There’s a free tier with 1,000 credits a month, but the binding limit is the 15-minute minimum interval between runs. Anything needing a fast reaction — lead alerts, ticket routing — needs Core at $9/month.

Is Make easier than Zapier?

No, it takes an afternoon rather than an hour to learn. It’s cheaper to run and more powerful for branching and batch work, and the visual canvas makes debugging clearer once you’re used to it.

Why is my Make scenario using so many credits?

Almost always the trigger fetching multiple records per run — each one makes every downstream module run again. Check the record limit in your trigger settings, and add filters early to stop unwanted records before they reach expensive modules.

How much does Make cost per month?

Free for 1,000 credits with a 15-minute interval limit. Core is $9/month for 10,000 credits, Pro $16 and Teams $29 — all at the same 10,000-credit entry tier, so the difference is features rather than capacity.

The Bottom Line

Make takes longer to learn than Zapier and costs less to run, and the visual canvas earns its keep the first time you debug something. Build this scenario, then spend five minutes understanding the trigger’s record-limit setting — it’s the one control that decides your bill.

Add an error handler before you trust it, name everything readably, and check your execution history after the first week. Once you can predict credit consumption from looking at a canvas, you understand Make properly.

Then build something with real payback — lead capture into your CRM is the standard next step. For a side-by-side comparison of all three platforms, see the automation tools guide, and the Zapier version of this walkthrough if you want to compare builders directly.

Want one practical automation you can set up in 15 minutes, delivered every Tuesday? Join the free newsletter.

Sources

• Make — Pricing plans
• Make Help Centre — Operations and how they are counted
• Zapier — Pricing plans
• n8n — Pricing plans
• SBE Council — 2026 Small Business Tech Use Survey

All sources retrieved 26 July 2026. Credit figures are worked arithmetic from Make’s documented counting rules. Interface wording changes — treat the step sequence as the shape, not as exact button labels.