How to use Make

Make.com runs scenarios: a chain of modules where the first one watches for something and the rest act on each bundle of data it passes along.

Make is more visual and more powerful than it first appears, and its pricing is based on operations rather than workflows — which changes how you should design. Efficient scenarios are cheap scenarios.

What people actually use Make for

Move data between apps with branching logic
Process a list of records one at a time with iterators
Call an API that has no ready-made integration
Route records down different paths based on their content
Schedule bulk jobs overnight instead of on every change

Make in five steps

1
Create a scenario and add the trigger module
Instant modules fire on a webhook; scheduled ones poll. Choose the polling interval deliberately — every check costs operations.
2
Run once to load real data
Click Run once so the following modules can see actual field names. Mapping against blank structures is the main source of broken scenarios.
3
Add filters between modules
Click the wrench on a connection and set a condition. Filtering early stops unnecessary modules running and keeps your operation count down.
4
Use routers for branching
A router splits the flow into paths, each with its own filter — one scenario handling three cases instead of three near-identical scenarios.
5
Set error handling and schedule it
Right-click a module to add an error handler (Resume, Ignore or Break). Then set the schedule and switch the scenario on.

Stuck on your own screen?

Paste a screenshot of the exact Make screen you're on and Magic Assist AI tells you what to click next — no course, no 40-minute video.

Teach me Make

Common Make mistakes

Polling every minute out of habit

A one-minute interval is over 40,000 checks a month. Use a webhook or a sane interval and the same scenario costs a fraction.

Forgetting the iterator

When a module returns an array, later modules see one bundle unless you iterate. This is the number one "only the first item worked" bug.

No error handlers

Unhandled errors deactivate the scenario after repeated failures, and you find out when the data stops arriving.

Mapping by hand

Pick fields from the mapping panel. Typed paths break silently when the structure changes.

Make FAQ

What is an operation in Make.com?

One module doing one piece of work on one bundle. A scenario with five modules processing ten records uses roughly fifty operations, which is what your plan meters.

Make vs Zapier — what's the difference?

Make is cheaper at volume and far better at branching, iteration and API calls. Zapier is simpler for straightforward two-app automations.

Why does my scenario only process the first record?

You're missing an Iterator. Modules receive one bundle at a time, so an array must be split before later modules see each item.

Can Make call any API?

Yes, with the HTTP module — you supply the URL, method, headers and body, which covers services with no dedicated integration.

More guides

Or search any software and get a plan built on demand.