How it works
A scenario in Make is an automated workflow. Its building blocks are modules, and each module belongs to an app and does one task: watch for new rows, create a record, send a message. You lay the modules out on a canvas and draw the path the data takes. The picture is the program, which makes branching and looping easier to follow than a list of steps.
Make is strong at handling data in bulk. A module can return many items at once, which Make calls bundles, and later modules run once for each. Built-in tools split lists apart, merge them back together, route items down different branches and catch errors. That power is also where newcomers get lost, because a scenario that handles 500 rows performs far more work than one that handles a single row.
Usage is measured in credits, which Make describes as what you pay for the operations your scenarios perform. More modules and more items mean more credits. Creators meet Make as the middle option: more flexible than a simple trigger and action tool, less technical than self-hosting n8n. Plans, credit allowances and prices change, so check Make's own pricing page.
A worked example
A creator keeps content ideas in a spreadsheet and wants each approved idea turned into a task with a due date.
- A module watches the sheet for rows where the status column says approved.
- A router sends video ideas down one path and newsletter ideas down another.
- Each path creates a task in the project tool, with its own rule for the due date.
- On a day with 20 approved rows, each module after the first runs 20 times. That is the work the scenario's usage is counted on.
An illustration, not a real account. Any numbers in it are made up to show the method, and are not benchmarks.
Common mistakes
- Looking for Integromat. It is the old name, and the product is now Make.
- Forgetting that every item multiplies the work. A module that runs once for each row is counted once for each row.
- Leaving errors unhandled. Without an error route, one bad item can stop a scenario.
Questions people ask
Is Make the same as Integromat?
Yes. Integromat was renamed Make. Older tutorials that mention Integromat describe the same ideas, though the screens have changed.
What are credits and operations in Make?
Make says operations count the activities performed in your scenarios, and credits are what you pay for those activities. A scenario with more modules or more items uses more.
Should I use Make or Zapier?
Zapier is simpler for short links between apps. Make gives you more control over branching and bulk data, with a steeper learning curve. Try your real workflow in both.
Sources
Make's announcement introduces Make as the name of its brand, business and new flagship platform, and says support for Integromat would be discontinued in 2023.
Make: Integromat evolves to Make read 13 October 2026
Make says operations count the activities performed in your scenarios, and credits are what you pay for those activities.
Make defines a scenario as an automated workflow that connects apps and services, and modules as its building blocks.
Make Help Center: What's a scenario and which type should you use?
Every link was opened on 13 October 2026. Products and policies change, so check the source before you rely on a figure.