Make

What it is

Make (formerly Integromat) is a visual workflow automation platform aimed somewhere between Zapier’s ease and n8n’s depth. Where Zapier is fundamentally a list of “if A then B” rules, Make models workflows as flowcharts with explicit routers, iterators, aggregators, and error handlers — closer to how a developer would draw it on a whiteboard.

It runs as a managed cloud service. Make bills in credits: most non-AI module operations use credits on an operation basis, while some built-in AI features can also vary with token or other usage. Model a representative scenario instead of treating every workflow as a fixed operation count.

Who it’s for

Make’s sweet spot is the non-developer who has outgrown Zapier. Marketing ops, RevOps, customer success teams who hit Zapier’s “this is technically possible but really painful” wall — they tend to land on Make and stay. The visual model is genuinely better at expressing branching logic than Zapier’s path system, and it forces you to think about error paths up front.

It’s a poor fit for engineering teams who want to self-host or who’ll inevitably need to drop into JavaScript. Those people belong on n8n, Pipedream, or Windmill.

Strengths

• Visual model. Routers, iterators, aggregators, and error handlers are visible objects on the canvas. Compared with Zapier’s nested paths, Make workflows are easier to hand off to a teammate three months later.
• Integration depth. Make publishes a broad app catalog, but the useful unit is whether each required trigger and action exists.
• Credit billing. Most non-AI operations map to credits; built-in AI and other features can use different credit rules.
• Template gallery. A real library, not the polite Zapier “Top Zaps” page. Useful for cold-starting a workflow.

Weaknesses / Watch out

• No self-host. This is a strategic choice — Make is firmly cloud-only. If your organization has data residency requirements, look elsewhere.
• Credit consumption. Iterators, aggregators, routers, and retries can multiply module operations and therefore credit use. Inspect scenario history with real data.
• Vendor ownership. Make is managed-only, so deployment and roadmap control stay with the vendor.
• Affiliate opacity. The Partners page on make.com is mostly Technology Partners (ISVs). The actual revenue-share affiliate program runs through PartnerStack and the commission rate isn’t posted publicly until you apply.
• Lock-in. Scenarios export to a JSON blueprint, but module logic is Make-specific; migrating to n8n or Activepieces means redoing the work.

Best paired with

• HubSpot or Pipedrive — Make’s deep CRM modules are where it earns its keep against Zapier.
• OpenAI or Anthropic via the dedicated AI modules — competent but not as flexible as wiring them into n8n’s AI nodes.
• n8n as a comparison tool — if you find yourself reaching for Make’s code modules a lot, the migration math may favor n8n.

Pricing reality check

Make replaced “operations” with credits as its billing unit. Most non-AI module runs still map to credits, while Make’s built-in AI features can have dynamic token-based credit use. Check the current pricing page, then replay a representative scenario to measure credits before committing to a plan; iterators, aggregators, data operations, and retries can change the total.

Verdict

Conditionally recommended. Make is the right pick if your team is non-technical, your workflows are visually complex, and your data can live in a cloud SaaS. For developer-leaning teams or anyone wanting self-host, n8n wins. For simple linear automations on long-tail SaaS, Zapier still wins on integration count and learning curve. Affiliate terms exist but you have to apply to see them, which is a small ding.

Sources

• Official site & pricing: https://www.make.com and https://www.make.com/en/pricing
• Partners page: https://www.make.com/en/partners
• Make on PartnerStack: https://market.partnerstack.com/ (search “Make”)
• Operations explained: Make operations documentation