What Is Make.com? Scenarios, Modules and Operations Explained

What Make.com is

Make (formerly Integromat) is a visual automation platform. Instead of a vertical list of steps, you build automations on a canvas, dragging modules around and connecting them with lines. It sits between Zapier and n8n: more powerful than Zapier for complex logic, and easier than n8n for people who do not code.

Make connects to more than 2,000 apps and has an HTTP module for anything it does not support directly.

Key Make terms

• Scenario: one automation, the equivalent of a Zap in Zapier or a workflow in n8n.
• Module: one step in a scenario, such as "Watch rows" in Google Sheets or "Create a contact" in HubSpot.
• Trigger: the first module, which starts the scenario. Some triggers are instant (webhooks), others run on a schedule.
• Router: splits the flow into several branches.
• Filter: a condition placed on the line between two modules. Data only passes if the condition is true.
• Iterator and aggregator: an iterator splits a list (for example, the line items of an order) into separate bundles; an aggregator combines bundles back into one.
• Bundle: one piece of data moving through the scenario, such as one row or one email.
• Operation / credit: one module run. This is what Make bills for.

How scenarios run

A scenario starts with a trigger module. If the trigger is scheduled, Make checks for new data at the interval you choose (every 15 minutes on Free, down to every minute on paid plans). If it is instant, it runs the moment an app sends data to its webhook.

Every bundle then flows left to right through the modules. If a trigger returns 10 new rows, the following modules each run 10 times, once per bundle.

Make also has strong error handling. You can attach error handler routes such as Resume, Ignore, Break or Rollback to any module, which is more control than Zapier gives you.

Make pricing: operations and credits

Make bills in credits. For standard apps, one module action is one credit (Make previously called these operations; the name changed but the maths did not). AI modules can use extra credits based on tokens.

Plan	Price	Credits per month	Notes
Free	$0	1,000	2 active scenarios, 15-minute minimum interval
Core	About $10–12/month	10,000	Unlimited scenarios, 1-minute interval
Pro	About $18–21/month	10,000	Priority execution, full-text log search, custom variables
Teams	About $32–38/month	10,000	Team roles and shared templates
Enterprise	Custom	Custom	Security and support add-ons

Prices from make.com, October 2026. The lower figure in each range is the annual-billing price. Larger credit packs are available on every paid plan.

Credits count every module, including the trigger. A scenario with a trigger plus four modules that processes 1,000 bundles a month uses about 5,000 credits. That is still usually much cheaper than the same volume in Zapier tasks.

Who Make is for

Make is a good fit if:

• You want visual logic with routers, loops and error handling.
• You run medium to high volume and Zapier has become expensive.
• You are comfortable reading JSON-like data and mapping fields.

Make is a weaker fit if:

• You need an app only Zapier supports.
• You need to self-host for data control (only n8n offers that).
• Your scenarios process large lists, where per-module credits multiply quickly.

Next steps

• Build your first scenario with our Make.com tutorial.
• See how terms map between tools in the automation glossary.
• Comparing costs? Read real pricing compared.