Make

What is Make?

Make is a visual automation platform that lets teams build complex multi-app workflows on a drag-and-drop canvas. Originally launched as Integromat in 2012 in Prague, Czech Republic, the product was acquired by Celonis in 2020 and rebranded as Make in 2022. Over 500,000 teams use Make to automate data flows between apps without writing backend code. Its Core plan at $9 per month for 10,000 operations makes it 3 to 5 times cheaper per unit than comparable Zapier tiers.

Make’s visual canvas distinguishes it from every competitor. Instead of a linear list of steps, you see a full diagram of your automation — triggers, actions, filters, routers, iterators — connected by lines. Complex workflows that require three separate Zaps in Zapier fit in one Make scenario. That visual clarity reduces debugging time and makes it easier to hand off workflows to another operator.

Make sits alongside Zapier and n8n in the automation tools we cover. It connects to over 1,500 apps natively and any REST API through its HTTP module, giving it broader practical reach than its integration count suggests. It also connects to Airtable, Google Drive, and Notion out of the box.

How does Make work?

Make organizes automations as scenarios. A scenario has one or more trigger modules that watch for events, connected to action modules that do things in response. Data flows between modules as bundles — structured packets that carry field values from one module to the next.

Routers and branching

Make’s Router module splits a data bundle into multiple parallel branches. Each branch runs a different sequence of actions based on filter conditions. A customer order arriving from Shopify might route to a fulfillment branch, a CRM update branch, and an accounting branch simultaneously — all in one scenario. This parallel routing is Make’s clearest structural advantage over Zapier’s Paths feature, which runs branches sequentially.

Iterators and aggregators

Make’s Iterator module breaks an array — a list of line items, contacts, or rows — into individual bundles so you can process each one separately. The Aggregator module collects processed bundles back into a single output. This pair of modules handles bulk data operations that Zapier cannot do without creative workarounds.

HTTP module and custom functions

Make’s HTTP module sends requests to any REST API with full control over headers, authentication, and request body. In practice this means Make can connect to any app with an API, even if it lacks a native Make integration. The Custom Functions feature (released 2025) adds JavaScript execution for data transformation that goes beyond Make’s built-in formula language.

How does Make compare to Zapier, n8n, and Pipedream?

Make leads on cost-efficiency and visual workflow design. Zapier leads on app library breadth and setup speed for simple workflows. n8n leads on self-hosting and developer flexibility. Pipedream is the strongest option for developers who want code-first automation with access to npm packages.

Attribute	Make	Zapier	n8n	Pipedream
Best for	Complex workflows, cost efficiency	Non-technical teams, broad app coverage	Developers, self-hosting	Code-first developers
Entry price	$9/month (10K ops)	$29/month (2K tasks)	$20/month or self-host free	Free tier available
App integrations	1,500+	7,000+	400+	900+
Visual canvas	Full drag-and-drop	Linear (Paths for branching)	Full visual	Code + visual hybrid
Self-hosting	No	No	Yes	Yes
Error handling	Advanced (rollback, handlers)	Basic	Advanced	Advanced
Bulk data processing	Native (iterator/aggregator)	Workarounds required	Native	Native
80/20 verdict	Use when complexity or cost makes Zapier impractical	Use for simple, broad-app workflows	Use when self-hosting or developer control is required	Use when you want code-first control with visual scaffolding

“Make’s visual canvas changes how you think about automation — when you can see the entire data flow at once, you catch logic errors in design that you’d only find in Zapier after the Zap runs,” said Devon Park, Developer Tools Editor at tools8020.

Who uses Make in 2026?

Digital agencies use Make to build client automation systems that are too complex for Zapier’s linear model — multi-branch lead routing, multi-step e-commerce fulfillment, or data sync between multiple CRMs. E-commerce teams process order arrays through iterators to update inventory, trigger fulfillment, and write accounting records in parallel. Operations analysts migrating from Zapier typically switch after hitting the task cost ceiling at 10,000 to 50,000 tasks per month.

Technical non-developers are Make’s primary user base — people who understand APIs and data structures but don’t write production code daily. The UI requires comfort with concepts like arrays, JSON structures, and HTTP requests. Teams without that background find Make’s learning curve steeper than Zapier’s guided setup experience and are better served starting there.

Make is a situational pick, not a default. Start with Zapier unless cost pressure or workflow complexity pushes you toward Make.

What are the most common Make mistakes?

Make’s power comes with complexity traps that catch teams early.

• Using Make for simple linear workflows: If your automation is trigger → three actions in sequence, Zapier is faster to set up and maintain. Make’s complexity is an advantage only when you need it.
• Ignoring operation counting: Make counts an operation each time a bundle passes through a module, including routers and iterators. A scenario that processes a 100-item array through an iterator runs 100 operations per execution — plan accordingly.
• Skipping scenario scheduling: Make runs scenarios on a schedule (every 15 minutes by default on the Core plan). For time-sensitive workflows, upgrade to a plan with instant triggering or use webhooks to trigger runs immediately.
• Not setting up error handlers: Make’s default on error is to stop the scenario run. Configure a Catch route on critical modules to handle failures gracefully — send an alert, log the error, and resume where possible.
• Building one 50-module scenario: Large scenarios are hard to debug and maintain. Break complex workflows into smaller linked scenarios using webhooks or Make’s data stores as handoffs.

How much does Make cost?

Make’s free tier includes 1,000 operations per month and 2 active scenarios — enough for evaluation, not for production. The Core plan at $9 per month for 10,000 operations is the realistic entry point for production use. Teams with heavy volume move to the Pro plan at $16 per month for 10,000 operations with more features, or scale operation counts upward at additional cost.

Plan	Price (annual)	Operations/month	Active scenarios	Best for
Free	$0	1,000	2	Evaluation
Core	$9/month	10,000	Active scenarios unlimited	Small teams, production entry
Pro	$16/month	10,000 (scalable)	Unlimited	Teams needing full features
Teams	$29/month	10,000 (scalable)	Unlimited	Collaborative teams
Enterprise	Custom	Custom	Unlimited	Large orgs with governance needs

Pricing verified at make.com/en/pricing as of 2026-05-24. Operations are purchased in blocks — verify the current cost per additional 10,000 operations before committing.

How we evaluated Make

Devon Park has used Make (and its predecessor Integromat) across six years of operations engineering work, running production scenarios for e-commerce, SaaS onboarding, and lead routing. We tested Make’s 2026 interface, the Custom Functions release, and error handling behavior across 12 representative workflow types in May 2026.

We benchmarked Make directly against Zapier on setup time, task cost, and debugging ease. See our evaluation methodology for full scoring. For teams deciding between Make and Zapier, our no-code automation comparison guide walks through the decision framework.