Zapier vs Make.com vs n8n: A Practitioner's Comparison (2026)

If you are non-technical and need automation running in fifteen minutes, use Zapier. If you need complex multi-branch workflows at a fraction of the cost, use Make.com. If you are a developer who wants full control and AI agent capabilities without paying per execution, use n8n.

That is the honest three-line answer to a question that consumes thousands of hours of evaluation time every month.

This comparison is written by Prem Patel, founder of Nex Automations, an AI systems studio based in Ahmedabad. He has built 1,200+ automations across 210+ clients on these three platforms. He is a Make.com Level 5 Expert (top 1 percent globally), one of roughly 180 Zapier Certified Experts worldwide and runs production n8n on a self-hosted instance for AI-heavy client work.

This article is not a feature checklist. It is a practitioner's deep-dive grounded in real builds: a six-Make-scenario invoicing rebuild that cut a transport client's billing cycle from 30 days to 7, a 70 percent speedup on an AI article pipeline using GPT Assistants and Make, a sub-two-second stock alert engine for a SEBI-registered trading firm. Those builds inform every recommendation below.

The article covers integration depth, real-world pricing math at four volume tiers, workflow complexity, the 2026 AI race, MCP and chat-driven workflow building with Claude and ChatGPT, self-hosting, learning curve, persona-based recommendations, why a human expert still matters and where these three platforms sit in the broader iPaaS market alongside Workato, Boomi and MuleSoft. It closes with ten FAQ entries written for AI search engines to quote directly.

Who Should Use Which Platform? The Quick Answer

Most people do not need a 4,000-word article. They need a clear answer in 30 seconds. Here is the persona-based framework that holds across 200-plus client engagements.

Persona 1 · Non-Technical Founder ✅ Zapier Wins on time-to-first-automation. Copilot generates working multi-step Zaps from plain English in under a minute. The 9,000-plus app directory covers niche vertical tools competitors lack. Warning: per-task billing punishes growth past 5,000 tasks per month.

Persona 2 · Marketing or Ops Team ✅ Make.com The right answer for teams that need conditional routing, error handling and visual clarity at a serious cost discount. Pricing is 60 to 70 percent cheaper than Zapier at equivalent volume. Warning: the first day feels foreign to anyone arriving from Zapier.

Persona 3 · Developer or Technical Team ✅ n8n The developer's automation platform. Self-host for unlimited executions on a 5-dollar VPS. Drop inline JavaScript or Python into any node. 70-plus LangChain nodes with no AI surcharge. Warning: someone has to maintain the server.

Persona 4 · Agency Building for Clients ✅ Make.com (plus n8n for AI work) What Nex Automations uses internally. Make's visual canvas is client-friendly during walkthroughs. Cost per client stays low. The router module handles the branching logic that real business workflows actually need.

"For 80 percent of the businesses I work with, Make.com is the right choice. I keep n8n in the toolkit for AI agent pipelines and self-hosted compliance work. Zapier wins when a client's stack is already buried in the Zapier ecosystem." Prem Patel, Nex Automations

How Many Apps Does Each Platform Actually Connect To?

Zapier connects to 9,000-plus apps. Make.com connects to 3,000-plus apps plus an HTTP module for any REST API. n8n offers 524 core nodes plus more than 5,800 community-published npm nodes and a Code node for anything else.

Those are the verified May 2026 numbers from each platform's public integration directory. The headline number is the worst way to choose a platform.

Why Raw App Counts Mislead

Almost every business runs on the same 10 to 20 core apps: HubSpot, Shopify, Slack, Google Workspace, Airtable, Stripe, Notion, ClickUp and one or two CRMs. All three platforms cover these completely.

What changes between platforms is depth per integration. Zapier may list a tool but only expose three triggers and four actions. Make's module set for the same tool often runs 15 to 25 deep. n8n exposes raw API endpoints behind a typed interface and lets a developer extend further with the HTTP node.

Where Zapier Wins

Niche vertical tools. Industry-specific CRMs, regional accounting software, obscure scheduling apps. Zapier's developer platform has a longer tail. If a client's stack includes a tool nobody outside their industry has heard of, Zapier is the safest bet.

Where Make.com Wins

Depth and HTTP coverage. The Make HTTP module handles OAuth 2.0, custom headers, multipart uploads and binary data better than Zapier's webhook step. Across the 1,100-plus Nex Automations builds shipped to date, no project has failed because Make lacked a native integration. The HTTP module handles anything with a documented API.

Where n8n Wins

Unlimited custom integrations. The HTTP and Code nodes accept arbitrary APIs, arbitrary auth schemes and inline JavaScript or Python. For a developer team integrating an internal microservice that no SaaS vendor will ever support natively, n8n is the only sensible choice.

"I have never lost a client project because Make.com lacked an integration. The HTTP module handles every documented API. The same is true for n8n. Zapier wins only when the niche app does not expose a REST API." Prem Patel, Nex Automations

What Does Each Platform Actually Cost? (Real Math, Not Marketing Pages)

A 5,000-run-per-month workflow with eight steps costs around 389 dollars on Zapier, around 51 dollars on Make.com and around 65 dollars on n8n Cloud. The same workflow runs for under 15 dollars on a self-hosted n8n VPS. The pricing gap is not marketing spin. It is the structural counting model.

How Each Platform Counts Work

Zapier counts tasks. One task equals one successful action step. A five-step Zap that runs 1,000 times consumes 5,000 tasks. Filters, paths and formatter steps do not count. MCP server calls cost two tasks each.

Make.com counts credits. The platform switched from "operations" to "credits" on August 27, 2025 with a 1-to-1 conversion. A standard module execution costs one credit. AI modules consume variable credits depending on token usage. Polling triggers cost one credit per scheduled check even when nothing new arrives.

n8n counts executions. One workflow run equals one execution regardless of how many nodes the workflow contains. A 20-node workflow run 1,000 times consumes 1,000 executions. Self-hosted n8n is unlimited. The user pays only for server costs.

The Cost Comparison at Four Volumes

Verified against May 2026 published pricing pages. Zapier prices reflect annual billing on the Pro tier task slider. Make.com prices reflect the Pro tier credit slider. n8n Cloud reflects monthly billing rates.

At 5,000 runs per month, Make is 87 percent cheaper than Zapier. Self-hosted n8n is 97 percent cheaper than Zapier. Those gaps widen as volume grows.

"Migrating a marketing client from Zapier to Make.com on the same workflow set saved them 720 dollars a year. The second client we migrated was running closer to 50,000 tasks a month. They saved 11,000 dollars in twelve months." Prem Patel, Nex Automations

The Hidden Costs Most Comparisons Skip

Zapier: Per-task counting compounds with multi-step Zaps. A small workflow change that adds two action steps can quietly multiply monthly cost by 40 percent. Heavy polling Zaps consume tasks even when the trigger returns no data.

Make.com: The credit system confuses new users. AI modules cost variable credits based on tokens. Iterators charge per loop iteration. Overage credits cost 25 percent more than the implied plan rate as of November 6, 2025.

n8n self-hosted: Server maintenance is not free. A small team will spend 2 to 5 hours per month on OS updates, database backups, SSL renewal and version upgrades. At a 50-dollar-per-hour cost basis that is 100 to 250 dollars per month of hidden labor. Below 10,000 executions per month, n8n Cloud is often a better deal than self-hosting once labor is priced in.

n8n Cloud: AI execution costs are real but invisible. AI nodes do not surcharge inside n8n but the LLM provider bills directly. A workflow that calls Claude or GPT-4 a thousand times per day will produce a separate OpenAI or Anthropic bill that nobody sees on n8n's invoice.

The Pricing Verdict

For most growing businesses running 5,000 to 50,000 operations a month, Make.com is the cheapest cloud platform that handles serious complexity. For developer teams comfortable with infrastructure, self-hosted n8n is unbeatable on raw cost. Zapier's pricing is justified only when its larger app directory closes a gap the others cannot.

Which Builder Handles Complex Workflows Best?

Make.com handles complex multi-branch workflows better than Zapier or n8n out of the box. n8n wins for developers who want code escape hatches alongside a visual canvas. Zapier is the cleanest builder for linear two-to-five-step Zaps and gets unwieldy past that.

That ranking holds across the 1,100-plus scenarios shipped through Nex Automations.

Zapier's Linear Builder

Zapier is a top-to-bottom step list. Trigger at the top, actions stacked below. The model is fast to learn. It struggles the moment a workflow needs branching logic or loops.

The Paths feature handles conditional logic but stacks vertically. By the time a Zap has three or more paths each with three or more steps, the screen looks like a fence. The Canvas product (GA 2025) helps visualize the bigger picture but does not change the underlying linear execution model.

What Zapier does brilliantly: a two-step trigger-action Zap from a Typeform submission to a Slack message. Built in three minutes. Ships the same hour.

Make.com's Visual Canvas

Make.com's canvas is the genuine differentiator. Scenarios sit on a graph where every module is a circle and every connection is a line. The data flowing between modules is inspectable at every step.

The router module is the killer feature. One module fans out into multiple parallel paths each with its own filter condition. The aggregator collapses them back. The iterator loops over arrays. The error handler runs a fallback path when a module fails.

Subscenarios shipped in October 2025 turned Make into a real engineering platform. A user can wrap a 20-module pattern as a reusable scenario and call it from any other workflow with typed inputs and outputs. Make Code (also October 2025) lets a developer drop JavaScript or Python inline.

The visual canvas matters when an automation specialist is explaining a build to a non-technical client. A six-router scenario can be walked through in five minutes. The same logic in Zapier would require switching between four open tabs.

n8n's Node-Based Canvas with Inline Code

n8n combines a visual graph with developer comfort. The Function node accepts arbitrary JavaScript. The Code node added Python support in 2024 and is now mature. The Merge node handles complex joins between data sources. Sub-workflows enable modular design with proper input and output contracts.

The defining n8n feature for engineering teams: workflows can be version-controlled in git on self-hosted instances. A team can branch, review and merge automation logic the same way they handle application code.

What n8n loses on: pure visual elegance. The interface is denser than Make's. A non-technical user looking at an n8n canvas for the first time will need 30 minutes of orientation. That same user can read a Make canvas in 5 minutes.

"When a client's workflow has more than three conditional paths, Make.com wins. Zapier's Paths feature works but the visual representation collapses fast. n8n gives the most control but the user has to think like a developer. Most clients do not." Prem Patel, Nex Automations

Which Platform Has the Best AI Features in 2026?

In May 2026, Zapier wins on AI breadth, Make.com wins on AI clarity inside a workflow, n8n wins on AI depth for developers. The right choice depends on whether the goal is "give my AI access to my apps," "build agents non-technical users can audit" or "build a custom RAG-and-agent pipeline."

All three platforms have meaningful AI stories. The differences are no longer about whether AI is supported. The differences are about how AI is exposed.

Zapier's AI Stack in 2026

Copilot is GA on all plans and now builds Zaps, Tables, Interfaces, Canvases and Agents from natural language.

Zapier Agents reached GA in 2025. Agents work across the full 9,000-plus app stack. They support agent-to-agent calling, pods for organization, live knowledge sources (Google Drive, Box, Dropbox), Chrome extension actions and version control. December 2025 added guest reviewers for human-in-the-loop workflows.

The Zapier MCP server exposes 30,000-plus actions to external LLMs like Claude, ChatGPT and Cursor. Each MCP tool call consumes two tasks.

BYOM (Bring Your Own Model) routes AI inference for Agents and Knowledge through the customer's AWS Bedrock account on Enterprise plans. AI Guardrails shipped in February 2026 and detects 30-plus PII categories, prompt injection attempts and toxicity. Tables, Interfaces and Chatbots are free on every plan as of September 2025.

Make.com's AI Stack in 2026

Make's next-generation AI Agents launched on February 11, 2026 on all plans. Agents are first-class objects inside the scenario canvas. The reasoning panel exposes the agent's chain of tool calls in real time. That visibility solves the black-box problem that haunts most agentic platforms.

The Maia conversational builder opened a waitlist at Waves 2025 in October. As of May 2026 the public Make site still shows waitlist language for Maia. Treat Maia as "rolling out" rather than fully GA.

Make exposes both an MCP server and an MCP client. Scenarios can be called as tools by external AI assistants. Scenarios can also call tools hosted on external MCP servers. Make Skills for Claude (a curated Claude integration) launched in 2025.

The AI Toolkit covers OpenAI, Anthropic Claude, Google Gemini, Stability AI and a growing set of native AI modules. AI module pricing uses variable credits tied to token consumption.

n8n's AI Stack in 2026

n8n ships 70-plus LangChain-based AI nodes (524 core nodes total in May 2026, with 93 of those in the @n8n/nodes-langchain package). The AI Agent node supports the Tools Agent, ReAct Agent, Conversational Agent and OpenAI Assistant patterns.

Native vector store integrations cover Pinecone, Qdrant, Supabase, PGVector, Milvus and MongoDB Atlas. Memory backends include Buffer Window, Postgres Chat, Redis Chat and Motorhead. Supported LLM providers include OpenAI, Anthropic, Google Gemini and Ollama for local models. NVIDIA Nemotron and NIM support landed in v2.22.0 on May 19, 2026.

n8n charges no AI surcharge. AI nodes count as standard executions. A 50-step RAG pipeline running 1,000 times still costs 1,000 executions. That is the structural advantage for AI-heavy work.

How Do MCP and Chat-Driven Building Actually Work in 2026?

MCP turned a chat session into a workflow trigger and, in one case, into a workflow builder. The three platforms expose this differently. Zapier connects a Claude or ChatGPT chat to 30,000-plus pre-configured actions. Make publishes scenarios as MCP tools and lets a Make scenario itself call external MCP servers. n8n is the only one of the three where an agent can actually create new workflows from chat as of April 2026.

Zapier MCP with Claude and ChatGPT. Setup takes around five minutes. A user creates an MCP server inside the Zapier MCP dashboard, picks which actions to expose, then pastes the generated server URL into Claude Desktop or ChatGPT Developer Mode. As of May 2026, the platform has processed 4.6 million tool calls across 195,000-plus MCP servers. Each call costs two Zapier tasks. Working chat patterns that ship today include "Read each unassigned Zendesk ticket, classify it by type and route it to the right team," "Pull Salesforce pipeline data, calculate a weighted forecast and push the summary to Slack" and "Find the brief in [Doc], write a 1,000-word draft, save it as a new doc." ChatGPT's Developer Mode MCP path is rougher than Claude's in practice. Community reports through April 2026 document OAuth state-loss bugs and tool-selection failures past 30 to 40 active tools per session.

Make MCP server and client. Make split MCP into two products. The MCP server (May 2025) publishes any "Active and On Demand" scenario as a callable tool with structured inputs and outputs. The MCP client (July 2025) lets a Make scenario itself call an external MCP server (GitHub, Webflow, PayPal, custom servers). MCP Toolboxes launched on March 24, 2026 and added team-scoped permissions, per-tool read-only and read-write controls and centralized invocation logs. Chat patterns that work today: "Run my weekly invoice scenario," "Trigger the onboarding sequence for [name]," "Pull this week's customer feedback responses." Editing a scenario from chat is not supported. The scenario builder still lives inside Make's canvas.

n8n MCP with workflow authoring. The April 29, 2026 update (v2.18.4 and above) shipped the most ambitious MCP integration of the three. A Claude or ChatGPT agent can now read, create, update, validate and execute n8n workflows through chat. The MCP server generates TypeScript that compiles and type-checks rather than raw JSON, which is the technical reason the workflows actually run on first try. A real example from the n8n blog: a single prompt asking Claude to build a workflow that emails a daily New York weather forecast at 7 AM produced a complete, validated and executing workflow. The user only had to plug in their Gmail address.

The 2026 AI Verdict

Zapier's MCP server is the most practical AI lever for non-technical users. Connecting Claude or ChatGPT to a Zapier MCP endpoint turns the AI assistant into an executor across the user's full app stack. That is genuinely useful out of the box.

Make's AI Agents feel different. The reasoning panel is the most under-rated AI feature of 2026. A user can watch the agent decide which tool to call. That visibility lets non-technical operators audit AI decisions, which is the gating problem for AI adoption in regulated industries.

n8n gives the most raw power. For a developer building an AI pipeline with custom retrievers, custom memory, custom tool routing and local model fallback, no other platform competes.

"Zapier MCP is the easiest AI win for a non-technical founder. Make's reasoning panel is the most interesting AI feature of 2026. For raw AI agent depth, n8n is still the best engineering platform." Prem Patel, Nex Automations

Can You Self-Host? And Does Data Privacy Matter for Your Use Case?

Only n8n supports self-hosting. Zapier and Make.com are cloud-only multi-tenant SaaS. For organizations with strict data residency requirements, that single fact closes the conversation. n8n becomes the only option.

The Self-Hosting Matrix

Zapier: No self-hosting. SOC 2 Type II audited annually. SOC 3 published. SAML SSO on Team and Enterprise. SCIM provisioning on Enterprise. Audit logs and immutable trails for all GA products. BYOM routes AI inference through customer AWS but the platform itself stays cloud-hosted by Zapier.

Make.com: No self-hosting. SOC 2 Type II certified. ISO 27001 certified. GDPR-compliant with EU data center option in Prague. SSO is Enterprise-tier only.

n8n: Full self-hosting via Docker, Kubernetes, npm install or systemd. SQLite (default, 10x faster pooling in n8n 2.0) or Postgres for production scale. Redis for queue mode. Air-gapped deployments supported. RBAC at Business plan and above. External secret stores include HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager and 1Password Connect (added April 2026). SOC 2 Type II on n8n Cloud. GDPR-compliant with EU Frankfurt hosting.

When Self-Hosting Actually Matters

Healthcare, finance and legal sectors with strict data residency rules. Pharmaceutical and clinical trial workflows under HIPAA. European companies operating under GDPR with strict third-party processor controls. Indian companies operating under DPDPA. Companies whose enterprise clients write contracts forbidding third-party SaaS processors. High-volume automation operations where per-execution cloud pricing turns prohibitive past 50,000 runs per month.

For everyone else, Make.com's cloud is compliant enough for any standard business use case. The decision to self-host should be driven by a legal or contractual requirement, not by intuition.

"If a client's enterprise contract forbids third-party data processors, n8n is the only option on this list. For everyone else, the cloud platforms are reliable and compliant." Prem Patel, Nex Automations

How Long Does It Take to Build Your First Automation on Each Platform?

Zapier delivers a working two-step Zap in 5 to 15 minutes. Make.com takes 30 to 60 minutes for the first scenario but pulls ahead by day three. n8n takes 1 to 2 hours for a developer comfortable with JSON and APIs. Non-technical users on n8n typically need 2 to 4 weeks of consistent practice to become productive. Most of them should be on Make or Zapier instead.

Zapier's Time-to-First-Automation

A first Zap takes 5 to 15 minutes. Copilot generates working multi-step Zaps from a description in under a minute. The interface is the cleanest of the three for absolute beginners. The trade-off arrives later when the user tries to build conditional logic.

Make.com's Time-to-First-Automation

The first scenario takes 30 to 60 minutes because the visual canvas is unfamiliar. By day 3 or 4, users build faster in Make than in Zapier because they can see the full workflow at once. The Maia builder will close the day-one gap further once fully GA. Nex Automations runs internal Make.com training for agency teams and the pattern is consistent. Week one is slower. Week two is faster.

n8n's Time-to-First-Automation

A developer comfortable with JSON, REST APIs and basic JavaScript ships a first n8n workflow in 1 to 2 hours. A non-technical user needs 2 to 4 weeks of practice before n8n feels comfortable. The interface assumes the user knows what a webhook is, how OAuth works and what a JSON path looks like.

"I teach Make.com to agency teams once a quarter. Every cohort follows the same curve. Day one feels slower than Zapier. By week two, every team is building twice as fast in Make because the visual canvas exposes the whole workflow at once." Prem Patel, Nex Automations

Building Is Easier Than Ever. So Why Do You Still Need an Expert?

Anyone with a Claude or ChatGPT subscription can now build a working automation in fifteen minutes. The expert question changed from "can a non-technical person build this" to "can a non-technical person build this reliably, securely and at production scale." The honest answer is usually no. The structural reasons matter.

Chat Sessions Forget Yesterday's Work

MCP gives a chat session access to the user's app stack but every session starts blank. The agent does not know what was built last Tuesday. It does not know why one path was chosen over another. After four or five iterative sessions on the same workflow, the design intent lives entirely in the human's head. The moment that human leaves, the workflow becomes a black box. An expert carries that institutional memory and writes it down in a runbook.

Plan-Dependent Time Keeps Getting Wasted

The most common failure mode in 2026 looks like this. A founder spends three hours describing a workflow to Claude. Claude builds it in n8n via MCP. The workflow fails because a webhook needs OAuth approval that only a human can complete. The founder spends two more hours debugging through chat before realizing the agent has been guessing at the credential model. An expert would have completed the OAuth, validated the trigger and saved four hours of wasted plan tokens.

Credential Binding Still Needs a Human

Every platform requires a real person to authenticate every connected app. MCP cannot click through OAuth screens. It cannot complete two-factor flows. It cannot read a security question out of a password manager. An expert handles credentialing once, centrally, with service-account discipline that survives team turnover.

Edge Cases and Error Handling Get Skipped on First Pass

AI agents optimize for the happy path. A workflow that processes 100 invoices a day works fine in the demo. The first production month surfaces the four percent of invoices with non-standard formats, the polling trigger that occasionally returns duplicates and the third-party API that rate-limits at 5 PM IST every Friday. Error handlers, dead-letter queues and retry policies need deliberate design. An expert builds these in before the workflow breaks.

Governance Decisions Are Not Delegable

Which Make Toolbox tools are read-only versus read-write. Which n8n workflows expose to MCP at all. Which Zapier actions a marketing agent can call versus a finance agent. These are security decisions. An expert frames the policy. The AI executes inside it.

For most teams, the right pattern is to build the first 70 percent of a workflow with chat and an MCP-connected platform, then bring in an expert to ship the remaining 30 percent that determines whether the system lives for one quarter or five years.

After 1,200+ Automations, Here's What I Actually Recommend

After 1,200+ automations across 210+ clients, the recommendation pattern is clear. Make.com handles 80 percent of business automation needs at the lowest reasonable cost. n8n wins for self-hosted compliance and AI-heavy engineering work. Zapier wins when a client's stack is locked into the Zapier ecosystem or when a niche vertical tool only integrates with Zapier.

Choose Zapier If

You are non-technical and need something working today. You depend on a niche vertical tool that only Zapier supports. You run under 5,000 tasks per month and the cost does not matter. You want AI Agents working across your entire app stack with minimal setup. The 9,000-plus integration directory closes a gap that Make or n8n cannot.

Choose Make.com If

You need multi-branch workflows with conditional logic, routers, iterators and error handlers. You care about cost. Make is 60 to 70 percent cheaper than Zapier at the same volume. You want a visual builder that scales with complexity. You are an agency building automations for clients. You want AI-assisted scenario building with Maia's collaborative approach and AI Agents you can audit through the reasoning panel.

Full disclosure: the Make.com registration link is an affiliate link. Make.com became the recommended platform in this comparison because Nex Automations has shipped 800-plus scenarios on it, not because of the affiliate program.

Choose n8n If

You are a developer or have engineering resources on staff. You need to self-host for compliance, residency or contractual reasons. You are building AI agent pipelines with custom memory, custom retrievers and local model fallback. You run more than 10,000 executions per month and want execution-based pricing on a self-hosted VPS. You need inline JavaScript or Python in production workflows.

What Nex Automations Actually Uses

Make.com for 80 percent of client work. n8n for AI agent pipelines and any project requiring self-hosting. Zapier when a client's existing automation stack is already deep in the Zapier ecosystem and the migration cost outweighs the recurring saving.

Where Do Zapier, Make and n8n Actually Sit in the iPaaS Market?

The three platforms in this article do not show up on the same analyst reports as Workato, Boomi or MuleSoft. That is the most important framing to understand before comparing them to enterprise iPaaS tools.

Gartner Magic Quadrant for iPaaS (2025 and 2026)

The Leaders quadrant on the 2025 Gartner iPaaS MQ names Boomi, Informatica, Microsoft (Azure Integration Services and Power Automate), SAP and Workato. Challengers: Amazon Web Services, IBM, Oracle and Salesforce (MuleSoft). Visionaries: Celigo, Huawei Cloud, Jitterbit, SnapLogic and Tray.ai. Niche Players: Frends and Zapier.

Zapier's 2025 entry into the MQ as a Niche Player is significant. Gartner had previously excluded Zapier because the iPaaS MQ targets enterprise platforms with hybrid connectivity, API management, EDI support and governance. The 2025 inclusion reflects Zapier's enterprise push around SSO, audit logs and AI Guardrails. Make and n8n are not in the MQ at all as of the March 16, 2026 update. Workato has now appeared as a Leader for eight consecutive years.

Forbes Cloud 100

Workato has appeared on the Forbes Cloud 100 for ten consecutive years through 2025. Zapier has appeared multiple times: rank 24 in 2020, rank 13 in 2022, rank 24 in 2023 and rank 31 in 2024. Make, n8n, Tray.ai and Pipedream have not appeared. The Cloud 100 skews toward revenue and valuation, which explains the gap.

Historical Context

Zapier was founded in 2011, went through Y Combinator in 2012 and is largely bootstrapped on roughly 1.4 million dollars of disclosed primary capital. ARR reached around 310 million dollars in 2024 with last implied valuation near 5 billion dollars.

Integromat launched in 2016 in Prague and was acquired by Celonis in October 2020 for over 100 million dollars. The product rebranded to Make in 2022. Celonis's current implied valuation is in the 11 to 13 billion dollar range across third-party trackers.

n8n was founded in 2019 in Berlin, raised a 12 million dollar Series A in 2021, a 55 million euro Series B in March 2025 and a 180 million dollar Series C led by Accel in October 2025 at a 2.5 billion dollar post-money valuation. Total raised: roughly 240 million dollars.

G2 Captures What Gartner Misses

G2's Winter 2026 iPaaS Grid places Zapier, n8n and Activepieces as Leaders alongside Workato, MuleSoft, Boomi and Celigo. Zapier holds 844 reviews and a 94 satisfaction score. n8n holds 124 reviews at 75. Make's 172 reviews score 45 on satisfaction, the lowest in the iPaaS Grid. The Make score likely reflects ongoing pricing-model debates after the August 2025 operations-to-credits switch and the Celonis integration adjustments.

The bottom line: Gartner's MQ is the enterprise validation framework. G2 and Capterra capture the actual user voice in the SMB and mid-market segments where Zapier, Make and n8n compete most directly. For a fuller view of the broader iPaaS landscape including Workato, Tray.ai, Pipedream, Celigo, Boomi, MuleSoft, Latenode and Activepieces, see the companion Nex Automations iPaaS landscape guide.

Frequently Asked Questions

Is Make.com really cheaper than Zapier?

Yes, materially. At 5,000 workflow runs per month with eight steps each, Zapier's Pro tier costs around 389 dollars per month while Make's Pro tier with a 40,000-credit slider runs around 51 dollars per month. The cost gap widens with volume.

Can n8n replace Zapier completely?

For developer teams, yes. For non-technical teams, usually no. n8n covers the same workflow patterns as Zapier and adds inline code, but the learning curve is steeper. A typical non-technical operator takes 2 to 4 weeks to become productive in n8n versus 15 minutes in Zapier.

Which platform is best for e-commerce automation?

Make.com for Shopify and WooCommerce automations at any meaningful scale. Make has 15-plus modules for Shopify alone covering orders, customers, products, fulfillments and refunds. Zapier covers the same ground at higher cost. n8n requires more setup but offers full control.

Which has better AI agent capabilities in 2026?

n8n for developer-built AI pipelines because it ships 70-plus LangChain nodes with no AI surcharge. Make.com for non-technical users because the AI Agent reasoning panel exposes every tool call in real time. Zapier for the largest addressable app surface (its MCP server exposes 30,000-plus actions to Claude and ChatGPT).

Can I migrate from Zapier to Make.com easily?

Yes for most workflows. Zapier and Make use similar trigger-action concepts. A direct rebuild of a five-step Zap in Make typically takes 30 to 45 minutes. The trickier migrations involve Zapier Paths (which map to Make routers but with cleaner syntax) and Zapier formatter steps (which map to Make's parsing modules). Workflows using Zapier-only native integrations require HTTP module rebuilds in Make.

Is n8n safe to self-host for production workflows?

Yes when the self-hosted instance is configured correctly. n8n 2.0 (December 2025) shipped secure-by-default execution, sandboxed Code nodes and task runners isolated by default. Production deployments should use Postgres rather than SQLite, queue mode with Redis for high concurrency, external secret stores like Vault or AWS Secrets Manager, RBAC at the Business tier and regular OS patching. Hetzner and DigitalOcean VPS instances are common production hosts.

Which platform do most automation agencies use?

Make.com is the dominant agency platform in 2026. The visual canvas is client-friendly during walkthroughs. The cost-per-client stays low. Agencies handling AI-heavy work usually add n8n alongside Make for self-hosted AI agent pipelines. Hiring an automation expert who knows both is more useful than hiring a single-platform specialist.

Does Make.com work with Shopify and WooCommerce?

Yes, deeply. Make has native Shopify modules covering orders, customers, products, inventory, fulfillments, refunds and metafields. WooCommerce coverage is comparable. The Shopify webhook trigger fires within 2 seconds of an event, which is faster than Zapier's typical 1 to 2 minute polling cadence.

What's the best automation platform for beginners?

Zapier for absolute beginners. The Copilot can generate a working multi-step Zap from a plain-English prompt in under a minute. The interface assumes nothing about the user's technical background. Make.com becomes the right answer once the user understands what an API and a trigger are, which usually happens in week two.

How much does it cost to run n8n on a VPS?

Around 5 to 30 dollars per month for the server, depending on volume. Hetzner CX22 (2 vCPU, 4 GB RAM) runs around 4.50 euros per month and handles 10,000-plus executions monthly for most workflow profiles. DigitalOcean Basic Droplet at the same spec runs around 18 dollars per month. High-throughput n8n deployments (50,000-plus executions monthly) need queue mode, Redis and a Postgres host, which adds another 15 to 40 dollars per month.

Related guides

• What is Make.com? Complete Guide for 2026
• iPaaS Landscape 2026: Workato, Boomi, Tray.ai and More
• What to Look for When Hiring an Automation Expert

Ready to get the right platform decided and your workflows built? Book a discovery call: 30 minutes to assess your stack and scope the build. To try Make for free, start with this link for a Pro month on us.

About the author: Prem Patel is the founder of Nex Automations, an AI systems studio based in Ahmedabad, India. He has built 1,200+ automations across 210+ clients on Make.com, Zapier and n8n. He is a Make.com Level 5 Expert and Make Silver Partner, a Zapier Certified Expert and an instructor for the Era of No Code with 1,000+ students.