How to Use Make: The Beginner's Guide (First Scenario, Modules, Filters, and the Credit Line)

CodexFuse Team · 2026-10-29T14:41:05.652Z · 16 min read

A beginner tutorial for Make.com: build your first scenario, master modules, filters and routers, and understand the credit system and pricing.

How to use Make comes down to one working loop: connect your apps, arrange their steps on a visual canvas, and let the finished scenario run itself. Make.com is a no-code automation platform that moves data between the apps you already use — Gmail, Google Sheets, Slack, your CRM — without you writing any code. This beginner guide walks you through that whole loop, from your first account to your first live scenario, plus the credit system that decides what you pay. If you would rather run your automations on your own server instead of Make's cloud, the best VPS for n8n guide covers the self-hosted route.

One clarification before we start, because Google mixes two different "Makes": this guide is about Make.com, the visual automation platform (it was called Integromat until Make renamed it in February 2022). It is not about GNU Make, the command-line build tool developers use to compile software — that is a different product with a similar name, and nothing below applies to it.

What is Make.com?

Make.com is a visual, no-code automation platform that connects your apps and moves data between them automatically. You describe a workflow as a scenario — a chain of steps on a canvas — and Make executes it every time a trigger event happens, on a schedule, or on demand. Make connects more than 3,000 apps out of the box, and anything else with a public API can be reached through its HTTP modules. Since 2025, Make has also offered AI agents that decide on their own which steps to take inside a scenario, plus an MCP server that lets outside AI assistants such as Claude or ChatGPT trigger Make scenarios. (Source: Blinno, "Make Automation for Beginners: Your First Scenario," fetched October 29, 2026.)

The four terms that explain everything

Every Make.com tutorial throws four words at you. Learn these once and every other guide makes sense.

Two truths no beginner guide leads with: first, a scenario is a chain of modules, not a single action — and the trigger module decides everything downstream, so picking the trigger is the first real decision, not the app. Second, credits are spent per module action, not per scenario run — a five-module scenario burns five credits every time it fires, so the free 1,000-credit line has to be counted before the scenario is built, not after. (Definitions: Blinno, fetched October 29, 2026; credit rules: Make's official pricing FAQ, checked October 29, 2026.)

What do you need before you start?

You need three things: a free Make account, one or two app accounts you already use (Gmail and Google Sheets work for the whole guide), and a realistic idea of your first scenario's size. The free plan gives you 1,000 credits per month and 2 active scenarios — enough to learn the platform and run a small real workflow. Sign-up is on make.com and takes a couple of minutes; you land on a dashboard with a big "Create a new scenario" button, which is where everything below happens. (Source: Blinno, fetched October 29, 2026; free-plan allowance confirmed on Make's pricing page, October 29, 2026.)

How to build your first scenario in Make

The fastest way to learn Make is to build one real scenario end to end. This one watches a shared inbox, asks an AI to categorise each new email, and routes it to the right place — the same example the best current beginner guides use, because it touches every core concept in five steps.

1. Create the scenario and add the trigger. Click "Create a new scenario" on your dashboard, then click the plus button in the middle of the editor. Choose Gmail and then "Watch Emails" — this is the trigger module that starts everything.
2. Connect Gmail and set the watch rules. Authorise your account through Google's sign-in (that is the connection). Set the folder to INBOX, the criteria to all emails, and "Maximum Results" to 1 while testing so each test run processes a single email.
3. Add the AI categorisation step. Add an AI module — from OpenAI or Anthropic — that reads the email and replies with exactly one category word. A prompt that works: "Assign the following email to exactly one of these categories: Marketing, HR, Finance, Other. Reply with the category name only." Pass the email text with the {{1.text}} placeholder (the text from module 1) and set the temperature low, for example to 0, so similar emails get classified the same way.
4. Split the paths with a router and filters. Add a Router from the Flow Control tools. It splits the scenario into paths — Marketing, HR, Finance, Other — and you put a filter on each path, for example "Category equals Marketing", so each email only travels down its matching route.
5. Attach the actions, test, then activate. On each path, add the destination module: a monday.com task, a Slack message, a forwarded email, a saved Drive attachment. Click "Run once" and watch the scenario execute with a real email. Only when the test run is clean, turn on scheduling and activate the scenario.

That is the complete first-scenario system: trigger → connection → AI step → router with filters → actions → test → schedule → activate. (Steps: Blinno, fetched October 29, 2026; the create → test → activate rhythm is also the shape of the Siznam beginner guide.)

How do triggers work in Make?

A trigger is the module that starts a scenario, and there are two kinds. Polling triggers check the app on a schedule — "Watch Emails" looks at the inbox every few minutes and picks up anything new. Instant triggers (webhooks) fire the moment something happens, because the other app pushes an event to Make. Polling is easier and works with almost every app; webhooks are faster and cheaper on credits because Make does not spend a scheduled check that finds nothing. If your scenario receives data from outside — a form submission, a payment event — point the webhook at Make and use a webhook tester first to see exactly what the incoming payload looks like before you map it into your modules.

What do filters, routers, and iterators do?

These three tools turn a straight line of steps into real logic. A filter sits between two modules and only lets data through when its condition is true — "only continue if the email category is Finance". A router splits one scenario into several parallel paths, each with its own filters, so one scenario handles many outcomes. An iterator takes a list — say, ten attachments — and runs the following modules once per item. Two cost details that matter: the router module itself costs zero credits, and so do error-handler modules (Rollback, Break, Resume, Commit, Ignore) — only the modules that actually touch data bill you. (Source: Make's pricing FAQ, checked October 29, 2026; router/filter mechanics: Blinno, fetched October 29, 2026.)

How does scheduling work in Make?

Every scenario runs on a schedule you choose: every 15 minutes, hourly, daily, weekly, or on a custom interval. Polling triggers run on this schedule, so the schedule directly controls how often your trigger checks cost you credits — a scenario that polls every 15 minutes burns 96 checks a day even on quiet days. Set the interval to match how quickly you actually need the result: an inbox router can wait 15 minutes, but a once-daily sales report should run once a day. If you need cron-style precision for a schedule you run elsewhere, a cron expression generator builds the exact pattern without you memorising cron syntax.

How do credits actually get spent?

Credits are simpler than they look: each module action costs one credit, AI modules can cost more, and routers and error handlers cost nothing. Work the maths before you build, using the free plan's 1,000 credits per month as your budget line.

The pattern to notice: a quiet personal workflow fits the free 1,000 credits; anything processing hundreds of items a day is a paid-plan workload. If you run out mid-month, Make lets you buy extra credits in bundles of 1,000 or 10,000, or turn on auto-purchasing of 10,000 credits before you run dry (Core, Pro, and Teams plans). Unused credits expire at the end of the term. (Source: Make's pricing FAQ, checked October 29, 2026.)

What does Make cost in 2026?

Make bills in credits, not in tasks, and the plan line is the monthly credit allowance. The free plan carries 1,000 credits per month and 2 active scenarios. With annual billing, paid plans start at $9 per month for Core (10,000 credits), then $16 for Pro and $29 for Teams — and billing is per organisation, not per person, so one plan covers the whole team. Prices move, so treat this table as the shape of the ladder and check Make's pricing page for the current numbers before you commit.

Make also sells a Start-up plan (50% off Business for teams under 20 employees) and enterprise tiers with apps like Workday, ServiceNow, and Greenhouse. (Sources: Blinno, fetched October 29, 2026; Make's pricing FAQ, checked October 29, 2026.)

Where do Make templates fit in?

Templates are pre-built scenarios for common jobs — lead capture, social posting, invoice filing — and they are the right starting point after your first hand-built scenario. Pick one close to your need, connect your own accounts, and read through its modules before you run it: a template teaches you the platform's idioms (how it names things, where it puts filters) faster than building from zero. The Make community around templates is also where you find answers when a module misbehaves — searching the community usually beats re-reading the docs. (Source: Siznam, "Make Guide For Beginners," via search October 29, 2026.)

What are Make AI agents and the MCP server?

Since 2025, Make has shipped two AI-native features worth knowing about even as a beginner. AI agents are modules that decide on their own which steps to take inside a scenario, instead of following your fixed path — useful when the right action depends on reading and judging content, like the email categorisation in our first scenario. The MCP server works the other direction: it lets outside AI assistants such as Claude or ChatGPT trigger your Make scenarios, so a chat answer can kick off a real multi-app workflow. Both cost more credits than plain modules, so budget them like the AI step in the credits table above. Treat agentic features with the same caution you would give any tool that clicks and types for you: test on copies of your data first. (Source: Blinno, fetched October 29, 2026.)

Make vs Zapier vs n8n: which should you pick?

The honest answer depends on what you are automating and where you want it to run. All three connect apps without code; they differ in control, cost shape, and hosting.

If you are choosing between Make and Zapier, start with the Zapier beginner guide and compare its first-task flow with the scenario you built above — Zapier is easier for quick simple tasks, while Make gives you more control and a visual layout for complex ones. If the self-hosted column appeals to you, the n8n beginner guide walks through the same concepts on your own server. (Comparison framing: Tecknospace, "What Is Make.com?," via search October 29, 2026.)

What mistakes do Make beginners make?

Most failed first scenarios come from the same short list, and every item on it is avoidable.

• No test data. Always click "Run once" with a real sample before you schedule anything. A scenario that has never run successfully will fail at 3 a.m. with your name on it.
• Missing filters. Unfiltered scenarios burn free credits on events you do not care about — a watch-everything trigger with no filter is how 1,000 credits vanish in a weekend.
• A giant first scenario. Build the smallest useful version, then extend it branch by branch. Debugging a 20-module scenario teaches you nothing; debugging a 4-module one teaches you the platform.
• Auto-publishing AI output. Let the AI draft and a human approve anything public — a categorisation mistake in an internal router is funny; a wrong auto-reply to a customer is not.
• Connecting accounts carelessly. Only connect apps through the official Make site, and use the minimum permissions each module needs. A connection is a key to that account — treat it like one.
• Never checking history. Silent failures hide until you look. Review your scenario's run history weekly, especially in the first month.

(Mistake list: AIToolSteps, "How to Use Make AI for Beginners," via search October 29, 2026.)

How do you map data between modules?

Data mapping is the quiet skill behind every working scenario: you drag fields from earlier modules into the inputs of later ones, exactly like the {{1.text}} placeholder in our first scenario. Two habits keep this painless. First, run the scenario once and inspect what each module actually output — the field names are often not what you guessed. Second, when a module hands you a blob of structured text, paste it into a JSON formatter to see the fields clearly before you map them. Most "my scenario does nothing" bugs are mapping bugs: the module ran fine, it just received an empty field.

Sources

• Blinno — "Make Automation for Beginners: Your First Scenario" (blinno.ch) — fetched in full October 29, 2026: what Make is, 3,000+ apps, Integromat rename February 2022, AI agents and MCP server since 2025, the four key terms, free plan 1,000 credits/month and 2 active scenarios, Core $9/mo annual (10,000 credits), Pro $16, Teams $29, per-organisation billing, first-scenario tutorial steps with the AI categorisation prompt and router filters.
• Make — Pricing & Subscription Packages (make.com/en/pricing) — checked October 29, 2026: credits as the billing unit, each module action typically one credit, AI modules may use more, router and error-handler modules cost nothing, extra credit bundles of 1,000 or 10,000, auto-purchasing on Core/Pro/Teams, free plan 1,000 credits = 1 data store, credits expire at term end.
• AIToolSteps — "How to Use Make AI for Beginners" (aitoolsteps.com) — via search October 29, 2026: free plan enough for multi-step scenarios, scenario/router/filter/AI-step vocabulary, the six beginner mistakes.
• Siznam — "Make Guide For Beginners: Start Automating Today" (siznam.co) — via search October 29, 2026: trigger → actions → test → activate steps, start simple, templates, community.
• Commswebb — "Automate Your Workflow with Make" (commswebb.com) — via search October 29, 2026: sign-up and first-scenario steps, filters and scheduling, use cases.
• Tecknospace — "What Is Make.com?" (tecknospace.com) — via search October 29, 2026: Make vs Zapier framing (Zapier easier for simple tasks, Make more control and visual layout).

Frequently asked questions

Is Make.com free?

Yes, to start. The free plan includes 1,000 credits per month and 2 active scenarios, which is enough to learn the platform and run one small real workflow. Paid plans start at $9 per month (Core, annual billing) when you outgrow it. (Sources: Blinno; Make pricing page, October 29, 2026.)

Do I need coding skills to use Make?

No. Make is a visual, no-code platform — you build scenarios by choosing apps, picking triggers and actions from menus, and connecting modules on a canvas. If you can describe your task as "when this happens, do that," you can build it in Make. (Source: AIToolSteps, October 29, 2026.)

What is a scenario in Make?

A scenario is one complete automation: a trigger module that starts the flow when an event happens, followed by action modules that do the work in your other apps. Scenarios can include filters, routers that split into paths, iterators for lists, and AI steps that summarise, classify, or draft text along the way. (Sources: Blinno; AIToolSteps, October 29, 2026.)

What is the difference between Make and Zapier?

Zapier is easier for quick, simple "when this, do that" automations. Make gives you more control — a visual canvas, routers, filters, iterators, and error handlers — so it handles complex multi-step workflows better. Pick Zapier for simplicity, Make for control. (Source: Tecknospace, October 29, 2026.)

Is Make.com the same company as the old Integromat?

Yes. Integromat was renamed to Make in February 2022. If you find older Integromat tutorials, the concepts still apply, but the interface and pricing details have changed since the rename — verify current facts on make.com rather than copying old guides. (Source: Blinno, October 29, 2026.)