What Is Make? The Automation Platform Explained
Make (formerly called Integromat) is a visual automation platform that lets you connect apps and services without writing code. You build automations called scenarios, which consist of modules that each represent an action in an app, such as receiving a form submission, transforming the data, and sending it to a CRM. Make supports over 1,500 app integrations and offers a free tier. It sits between simple tools like Zapier and more developer-oriented tools like n8n in terms of complexity and flexibility.
Make (formerly Integromat) is a visual automation platform that connects apps and services through scenarios built from modules.
How Make works: scenarios and modules
The core concept in Make is the scenario. A scenario is an automated workflow that runs when triggered by an event or on a schedule. Each scenario consists of modules arranged on a visual canvas.
A module represents a single action or operation in a connected app. Examples include:
- Watch for new rows in a Google Sheet (trigger module)
- Get customer details from a CRM
- Transform and format the data
- Create a record in another database
- Send an email notification
You connect modules by drawing lines between them on the canvas. Data flows from one module to the next, and you can map fields from earlier modules into the inputs of later ones. Make supports branching (different paths based on conditions), loops (iterating over a list of items), and error handling routes.
Make compared to Zapier
Zapier is the most widely known automation platform and is excellent for straightforward two-step automations: when this happens, do that. Make is more powerful for multi-step, branching flows. Some key differences:
- Make uses a canvas where you can see the full flow visually; Zapier uses a linear list
- Make lets you iterate over arrays natively; Zapier handles this less elegantly
- Make’s pricing model is based on operations rather than the number of Zaps, which can be more economical at scale
- Zapier has a simpler learning curve for non-technical users
For automations that involve multiple conditions, looping over data, or custom data transformations, Make is typically the better choice. For simple one-to-one integrations with popular SaaS tools, both platforms work equally well.
Make compared to n8n
n8n is a developer-oriented automation platform that can be self-hosted and supports writing custom JavaScript inside nodes. Make is a fully hosted, no-code product. The choice between them depends on your team’s technical capability and your need for control over infrastructure. n8n offers more flexibility for technical teams; Make offers a more polished experience for non-technical users. See also our article on n8n vs Power Automate for a broader comparison.
Who Make is for
Make is well suited for:
- Small and medium-sized businesses automating internal processes
- Operations and marketing teams who want to connect their tools without involving developers
- Consultants and freelancers building automations for clients
- Anyone who needs more logic than Zapier provides but does not want to manage their own server
The free tier is sufficient for exploring the platform and running low-volume automations. Most teams doing real automation work end up on a paid plan within a few months.
Common Make automation examples
Some typical scenarios businesses build in Make:
- Syncing new leads from a web form to a CRM and sending a welcome email
- Monitoring a shared inbox and routing emails to different team members based on keywords
- Pulling data from a Google Sheet, transforming it, and updating a database nightly
- Creating tasks in a project management tool when a new order arrives in an e-commerce platform
- Generating PDF invoices from form submissions and emailing them automatically
Our tip: Start by mapping your automation on paper before opening Make. Write down the trigger, each step, and what data you need at each step. This prevents you from building halfway through a scenario only to discover you need data from a module you already passed.
Frequently asked questions
What is the difference between Make and Zapier?
Zapier uses a linear Zap model where each trigger leads to one or more sequential actions. Make uses a visual canvas where you can branch flows, loop over arrays, handle errors, and build complex multi-path logic. Make is generally more capable for complex automations, while Zapier is simpler to learn for basic two-step connections. Make's pricing is based on operations per month rather than the number of active Zaps, which can be cheaper for high-volume use cases.
Is Make free to use?
Make offers a free tier that includes 1,000 operations per month and up to 2 active scenarios. Operations are the individual module executions within a scenario run. A scenario with five modules that runs 100 times uses 500 operations. Paid plans start at a low monthly price and scale with the number of operations. For teams with higher volumes or who need features like custom scheduling intervals and team collaboration, a paid plan is typically necessary.
What is an operation in Make?
An operation in Make is a single module execution within a scenario. Each time a module runs, whether it reads data, transforms it, or sends it to another service, it counts as one operation toward your monthly limit. A scenario with three modules that triggers 200 times per month uses 600 operations. Understanding operations is important when estimating your monthly usage and choosing the right plan.