Make Review (2026)

Make earns a 8.2/10 in our review. Visual automation that punches above its weight. Make (formerly Integromat) gives you a drag-and-drop canvas for building workflows with branching, loops, and error handling. It's 3-5x cheaper than Zapier at scale and far more flexible. The tradeoff is a steeper learning curve. It's built for teams that need complex automations without paying zapier's per-task premium, which means the strengths and weaknesses below should be read through that lens. A tool's score only matters in the context of who it's for.

Make starts at $9+/mo, putting it in the low-priced bracket for automation. The full pricing breakdown is in the table below, and our Make pricing page walks through the per-tier math and team cost calculations.

Visual drag-and-drop workflow builder with branching logic.

This is one of the reasons Make earned its 8.2/10 score. For teams that prioritize this capability, Make delivers it in a way that justifies the $9+/mo starting point. It's not the only tool in automation that does this, but it's one of the better options if it maps to your workflow.

3-5x cheaper than Zapier at equivalent volume.

This is one of the reasons Make earned its 8.2/10 score. For teams that prioritize this capability, Make delivers it in a way that justifies the $9+/mo starting point. It's not the only tool in automation that does this, but it's one of the better options if it maps to your workflow.

Real error handling with retry and fallback paths.

This is one of the reasons Make earned its 8.2/10 score. For teams that prioritize this capability, Make delivers it in a way that justifies the $9+/mo starting point. It's not the only tool in automation that does this, but it's one of the better options if it maps to your workflow.

Steeper learning curve than Zapier.

This is a real limitation worth weighing before you commit. It doesn't disqualify Make for everyone, but if this issue maps to a workflow that matters to your team, you'll feel it within weeks of adoption. The alternatives section below covers the tools that handle this better.

Fewer native integrations (1,500+ vs Zapier's 6,000+).

This is a real limitation worth weighing before you commit. It doesn't disqualify Make for everyone, but if this issue maps to a workflow that matters to your team, you'll feel it within weeks of adoption. The alternatives section below covers the tools that handle this better.

Documentation could be better for advanced scenarios.

This is a real limitation worth weighing before you commit. It doesn't disqualify Make for everyone, but if this issue maps to a workflow that matters to your team, you'll feel it within weeks of adoption. The alternatives section below covers the tools that handle this better.

Make starts at $9+/mo. The pricing table below shows every tier. For team math (what does this actually cost a 5-person team? a 25-person team?), see our dedicated Make pricing breakdown, which calculates real-world costs and flags hidden fees.

Whether Make is fairly priced depends on what you're comparing it to and which features you actually use. The competitive pricing in automation ranges widely, so the alternatives section below is the right next step if cost is your primary concern.

Buy Make if: Teams that need complex automations without paying Zapier's per-task premium. The tool earns its price for this audience, and the strengths above directly serve their workflow. If your team fits this profile, Make is a defensible pick.

Skip Make if: the cons above describe critical pain points for your team. The weaknesses we flagged are real and they don't disappear with a workaround. If any of them block your core workflow, look at the alternatives below.

Try before you buy: request a demo and run a 100-data-point test against your actual use case before signing an annual contract. Don't trust the marketing demos. Run your own data through the product before committing money.

If Make doesn't fit, here are the strongest alternatives in automation, ranked by overall score:

Zapier (7.8/10)

The easiest way to connect apps without code. Zapier's 6,000+ integrations make it the go-to for simple automations. But at scale, the per-task pricing adds up fast and the linear workflow model feels limiting compared to Make's visual approach. Starts at $19.99+/mo. Choose Zapier over Make if non-technical teams that need simple app-to-app automations matches your situation better than Make's target audience.

Our full best automation guide ranks every tool we cover in this category and explains the trade-offs between them.

Three things to plan for before you sign up for Make:

• Onboarding time. Budget at least one full week to get Make configured for your team's actual workflow, even if the vendor advertises a 5-minute setup. The 5-minute setup gets you a logged-in account. The week gets you a tool that fits the way you work.
• Data migration. If you're switching from another tool, plan the import carefully. Field mapping is where most automation migrations break. Run a small test batch (50-100 records) before importing the full dataset, and verify everything lands in the right place.
• Team training. Even simple tools fail if half your team doesn't use them. Schedule one short training session within the first week of rollout, and document the 5-10 most common workflows in a shared place your team can reference.

The teams that get the most value out of Make treat the first month as a structured rollout, not an experiment. Set a clear goal (what should this tool be doing for us by week 4?), measure against it, and adjust before you commit to an annual contract.

Make is a solid option for the right buyer. Its 8.2/10 score puts it in the upper tier of automation, but it isn't the category leader. The right way to evaluate it: confirm that the strengths above match your priorities, and that none of the weaknesses block your critical workflows. If both check out, it's a good pick.

For the team-cost math and per-tier breakdown, see Make pricing. For head-to-head comparisons, look for Make in our Automation category page.

The fastest way to validate Make for your specific situation: pull a small sample of your real data, run it through the product for two weeks, and measure against the workflow goal you set for adoption. The teams that get Make wrong almost always skipped this step and bought based on the demo. The teams that get it right always ran their own data through it first.