A beginner-friendly guide to building your first automation — no code, no confusion, just results.
Make is a visual automation platform. You connect apps and define logic — Make runs it for you, automatically, without writing a single line of code.
Every concept has a mental model — because knowing why you'd use something is more valuable than memorizing what it's called.
The main unit of work. A scenario is one complete automated workflow — a chain of steps that runs from left to right.
Think: a recipeA single step inside a scenario. Every circle on the canvas is a module — one action, one app, one thing happening.
Think: one ingredient in the recipeBefore a module can talk to an app (Gmail, Notion, Slack…), you need a Connection — Make's secure login to that app. Create it once, reuse forever.
Think: a key to the front doorOne record of data passing through your scenario. If 3 emails arrive, Make processes 3 bundles — one per email.
Think: one row of data in a pipelineA diamond-shaped module that splits your scenario into parallel paths. Each path can handle a different condition.
Think: an if/else fork in the roadA gate between two modules. Only lets a bundle continue if it meets your condition — doesn't add a step, it's on the line.
Think: a bouncer at the doorIterator breaks a list into individual items. Aggregator combines multiple items back into one. Used together to process lists.
Think: unpack → process → repackEvery scenario starts with exactly one Trigger. Everything after it is an Action or utility.
Watches for something to happen. Always the first module.
Does something — sends, creates, updates a record.
Retrieves data without changing anything.
Loops over or collects lists of items.
A quick map of the buttons and panels you'll actually use.
Your list of all automations. Click one to open it on the canvas.
Manage your app logins. Add, edit, or remove access here.
Make's built-in mini-database. Store data that needs to persist between runs.
Pre-built scenarios to steal and modify. A serious cheat code.
Runs the scenario one time right now. Use this obsessively while building and testing.
Numbers that appear on each module after a run. Click them to inspect every bundle — your debugger.
Turns the scenario on to run automatically. Always test first — never activate blind.
Mapped variables from earlier steps. Click a field → select a token = live data flowing through your scenario.
Follow these 9 steps to build and activate your very first automation.
Click "Create a new scenario" from the Scenarios dashboard.
Click the + in the center → search for your trigger app (e.g., Gmail) → pick a trigger event (e.g., "Watch Emails").
Click "Add a connection" → log in to the app and authorize Make. You only do this once per app.
Set which mailbox, folder, or label to watch. Set how many results to return on first run (keep it small — 1 or 2 while testing).
Click Run Once at the bottom. This fetches real data so your next module has something to work with.
Click the + on the right of the trigger → search for your destination app (e.g., Slack) → pick an action (e.g., "Create a Message").
Click into a field (like "Message") → pick purple tokens from the panel — Subject, Sender, Body — from the previous module. This is the magic.
Click Run Once and verify the message appears in Slack. Check the execution bubbles if something looks wrong.
Flip the Activate switch. Your scenario is now live and running automatically.
Bookmark this table. It covers 90% of the decisions you'll make while building.
| When you need to… | Use this |
|---|---|
| Run on a timer (every hour, daily, etc.) | Scheduled trigger + set the interval |
| Run the moment something happens | Instant / Webhook trigger |
| Only proceed when a condition is met | Filter on the connection line |
| Do different things based on conditions | Router module (diamond shape) |
| Process each item in a list separately | Iterator → modules |
| Combine multiple items into one | Aggregator module |
| Remember data between scenario runs | Data Store module |
| Something broke / unexpected result | Click execution bubble → inspect the bundle → read the error tab |
| Start faster, not from scratch | Templates — clone the closest one and modify it |
These will save you hours.
Every piece of data from a previous module is available as a purple token. Never retype something that already exists.
"Scenario 1" is useless in two weeks. Name it what it does: "New Lead → Slack Alert."
Test every step before moving to the next. Never activate a scenario you haven't run manually first.
Make's error messages are specific — they tell you exactly which field or permission failed. Don't skip them.
Find a template close to what you need → clone it → modify it. Way faster than building from scratch.
Stop unwanted bundles at the second module, not the last. This saves operations and avoids errors downstream.