AI automation

Make.com Tutorial for Beginners: Build Your First Useful Scenario

By Sauravjit Singh · Updated 2026-11-05 · 6 min read

Short answer: To build your first Make.com scenario, create a scenario, add a trigger module such as a webhook from your website form, add action modules like Google Sheets 'Add a row' and Gmail 'Send an email', map fields from earlier modules, test with 'Run once', then set the schedule and switch the scenario on.

Make (formerly Integromat) looks busier than Zapier at first: a canvas, circles, lines and a lot of settings. Once you know five or six terms, it becomes the more flexible of the two.

In this tutorial you'll build one scenario you can actually use: a website enquiry goes into a Google Sheet and triggers a Gmail alert showing the time in IST. Along the way you'll learn how operations are counted, so you don't use up the free plan while testing.

Make.com terms you need before you start

TermWhat it meansIn our scenario
ScenarioOne automation, drawn on a canvasWebsite enquiry alert
ModuleOne step (a circle on the canvas)Webhook, Sheets, Gmail
TriggerThe first module; starts each runCustom webhook receiving form data
BundleOne record passing through, like one enquiryOne form submission
MappingUsing data from an earlier module in a later onePutting the form's name field into the sheet
FilterA condition on the line between modulesSkip enquiries with no phone number
OperationOne module processing one bundle; what your plan countsThree per enquiry in this build
Data storeA small table inside Make for remembering thingsOptional: store processed IDs

How are operations counted in Make?

Each module that runs uses an operation, so a three-module scenario uses about three operations per enquiry. A scheduled trigger that checks for new data has typically used an operation even when it finds nothing, which is how free plans get used up.

As of November 2026, Make's free plan allows a limited number of operations a month (it has been around 1,000), and Make has been moving its plans towards credits, where AI modules can use more than a standard module. Check the current pricing page for exact numbers.

A quick calculation shows why this matters. Say you schedule a Google Sheets 'watch rows' trigger every 15 minutes, all day. That's 96 checks a day, roughly 2,900 a month, before a single enquiry is processed. An instant trigger like a webhook only runs when data arrives, so 60 enquiries a month at three modules each uses about 180 operations.

  • Prefer instant triggers (webhooks, instant app triggers) where available.
  • If you must schedule, limit it to business hours and a sensible interval.
  • Test with 'Run once' and a single sample, not by leaving the scenario on.

Build it: website enquiry → Google Sheet → Gmail alert

Say you run a coaching centre in Dwarka with an enquiry form on your website. Many form builders (Elementor forms, WPForms, Fluent Forms and others, sometimes via an add-on) can send submissions to a webhook URL. If yours can't, a Google Form that writes to a sheet works as the trigger instead.

  1. Create a Google Sheet named Enquiries with headers: Received (IST), Name, Phone, Email, Course, Message, Source page.
  2. In Make, click Create a new scenario. On screen you'll see one large empty circle with a plus sign.
  3. Click it, search Webhooks, choose Custom webhook, click Add, name it 'Website enquiry' and copy the URL Make gives you.
  4. Paste that URL into your form's webhook setting and submit one test enquiry. In Make, the webhook should show 'Successfully determined', meaning it now knows your form's fields.
  5. Click the half-circle on the right of the webhook to add a module. Choose Google Sheets, then Add a row. Connect your Google account and pick the Enquiries sheet.
  6. Map each column. Click into Name and select the name field from the webhook bundle; repeat for the rest.
  7. For Received (IST), don't use the form's raw time. Type formatDate(now; "DD MMM YYYY, hh:mm A"; "Asia/Kolkata") using the date functions panel. It writes a time like 14 Nov 2026, 07:45 PM.
  8. Add a Gmail module, Send an email. Send it to the person who calls enquiries. Subject: 'New enquiry: ' plus the Name and Course fields. Body: phone, message, the IST time and a link to the sheet.
  9. Click Run once at the bottom left, then submit another test enquiry. Each module shows a bubble with a number; click it to see exactly what went in and came out.
  10. Check the sheet row and the email. If both look right, save, switch the scenario on and choose 'Immediately as data arrives' for the webhook.

Add a filter so only real enquiries trigger alerts

A filter on the line between modules stops bundles that don't meet a condition. Spam submissions are the usual reason you'll want one.

Click the line between the webhook and Google Sheets, choose Set up a filter, and add conditions such as: Phone exists, and Phone length is at least 10 characters, and Message does not contain 'http'. Filtered bundles stop there, and in our experience the module after a filter uses no operations for that bundle, which also saves your plan.

The 5 settings beginners miss

  1. Scheduling: open the clock icon on the trigger. Webhooks can run immediately; polling triggers need an interval. A beginner mistake is leaving a polling trigger on a short interval overnight.
  2. Data store: if a trigger can send the same record twice, save each enquiry's ID in a data store and add a filter that skips IDs already seen.
  3. Error handler: right-click a module and add an error handler. 'Ignore' skips a failed bundle; 'Break' stores it as an incomplete execution so you can retry it. For leads, you want to retry, not ignore.
  4. Filters: covered above. Name each filter clearly ('Has phone number') so future-you knows why a bundle stopped.
  5. Run once: use it for every change. Editing a live scenario and hoping is how real enquiries get lost.

Also check scenario settings for storing incomplete executions, and set your profile's time zone to India so schedules and logs match your clock.

First-scenario errors and what they usually mean

Most first builds hit one of a handful of errors. Read the message in the module's bubble after a Run once; it usually points straight at the cause.

  • Webhook keeps waiting for data: the form isn't actually posting to the URL. Check you pasted the full URL, saved the form settings, and submitted after clicking Run once.
  • Sheet row added but columns are empty: the mapping points at a field name from an old test. Click Redetermine data structure on the webhook, resubmit, and remap.
  • Google or Gmail connection refused: re-create the connection and allow every permission Make asks for. Google Workspace admins sometimes block third-party apps, so ask whoever manages your company's Google account.
  • Times are 5 hours 30 minutes off: you used the raw time or your profile time zone is wrong. Use the formatDate function with Asia/Kolkata.
  • Duplicate rows: the form or plugin retried. Store submission IDs in a data store and filter repeats, as described above.

What to build next

Once this runs for a week, add one improvement at a time: a router that sends course-specific enquiries to different people, a WhatsApp alert, or an AI module that summarises long messages. Our guide to adding ChatGPT to Zapier and Make shows how to keep the AI output in a format later modules can use.

If you're still deciding between tools, our Zapier vs Make comparison sets out where each one is easier. And when a scenario stops running, start with our checklist of common reasons automations fail.

For the wider picture, from lead capture to invoices, see our hub on automating work with AI, no code needed. Make is one of the tools students build with in the Spettro School Applied AI Professional programme.

Frequently asked questions

Is Make.com free to use?

Make has a free plan with a limited monthly allowance of operations, which is enough to learn and run a small, low-volume scenario. Limits and plan names change, so check Make's current pricing page.

Is Make the same as Integromat?

Yes. Integromat was renamed Make in 2022. Older tutorials that mention Integromat still describe the same core ideas of scenarios, modules and operations, though the screens look different now.

Do I need coding to use Make.com?

No. You build scenarios by choosing modules and mapping fields with clicks. Some date and text functions use a formula-like syntax, similar to spreadsheet formulas, but no programming.

Why does my Make scenario use operations when nothing happens?

Scheduled triggers check for new data at every interval, and those checks typically use operations even when nothing is found. Use instant triggers like webhooks where you can, or schedule fewer checks.

What is 'Run once' in Make?

It runs the scenario a single time so you can watch each module's input and output. Use it to test every change before switching the scenario on.

Want to learn this with a trainer?

Leave your details and our counsellor will call you within one working day with batch dates, fees and the right course for you.

  • Free counselling call, no obligation to join
  • Weekday and weekend batches, online or offline
  • Small batches of 15 to 20 students

Or chat on WhatsApp

Enter a 10-digit mobile number.

We use your details only to contact you about Spettro School courses.

Chat on WhatsApp