What is Make?
Make (formerly Integromat) is a visual automation platform that sits between Zapier (simple, non-coders) and n8n (technical, code-heavy). Its canvas UI shows data flowing visually between "modules" — Make's term for operations. A Scenario is a workflow; a Module is a single unit of work. Connect modules and data flows through the canvas: more visual than Zapier, less code-heavy than n8n.
Make's standout feature: operations-based pricing. Where Zapier bills per task, Make bills per operation. At scale, Make is typically 5x cheaper than Zapier. One Make scenario run can consume 1–10 operations depending on modules used.
Core Concept: Scenarios vs Operations
Scenario
- Entire workflow (visual canvas)
- Multiple modules connected
- Executes on trigger
- Can run once or thousands of times
Operation
- Single unit of work
- One module = one operation
- Counted per module execution
- The billing unit (not per run)
Pricing key: 1 Zapier task ≈ 1 Make operation, but Make charges only for the modules that actually run. Complex scenarios with branches can use fewer operations than you'd expect.
Key Features
-
1
Drag Canvas
Visual scenario builder. See data flow between modules in real time. No code required for basic flows.
-
2
1,500+ Modules
Pre-built integrations (Google, Salesforce, Slack, etc.). More than Zapier in some categories, with a growing library.
-
3
Router Module (Branching)
Split logic: if A, go to path 1; if B, go to path 2. More powerful than Zapier's basic filters.
-
4
Iterator & Aggregator
Loop over arrays. Iterate a user list, process each, aggregate results. Zapier cannot do this natively.
-
5
Data Stores
Built-in key-value storage. Cache data, share state between scenarios, avoid re-fetching the same data.
-
6
AI Modules
GPT integration, text-to-speech, image generation modules. Limited compared to Zapier's native AI actions.
How Make Works
Design Scenario
Drag modules onto canvas. Connect them with edges. Map data between outputs and inputs. No coding required.
Set Trigger & Schedule
Webhook trigger or scheduled (hourly, daily, weekly). Test trigger with sample data before enabling.
Run & Monitor
Enable scenario. View Execution History: every run, inputs, outputs, and operations consumed.
Debug & Iterate
Failed run? Check history to see exactly where it broke. Fix module config, re-run. Repeat until working.
Use Cases
- → E-commerce data routing: Order from Shopify → Check inventory → Send to warehouse OR backorder list depending on stock.
- → Lead enrichment: Form submission → Look up company data → Add to CRM with enriched fields → Notify sales.
- → Bulk document processing: Folder of PDFs → Iterate each → Extract text → Save to database.
- → Multi-channel notifications: Slack → if urgent, also email, SMS, push. Different paths for different severity levels.
Pros and Cons
Pros
- + 5x cheaper than Zapier at scale
- + Best visual canvas of any no-code tool
- + Routers & iterators (advanced logic)
- + 1,500+ integrations
- + Data stores for state sharing
- + More powerful than Zapier without code
Cons
- - Canvas gets cluttered with complexity
- - No code nodes (unlike n8n)
- - Operations quota can be confusing
- - Steeper learning curve than Zapier
- - Some integrations less polished
- - Not self-hostable
Make vs Zapier vs n8n
| Feature | Make | Zapier | n8n |
|---|---|---|---|
| Pricing Model | Operations ($9+/mo) | Tasks ($20+/mo) | Free self-hosted |
| Visual Canvas | Best | Linear | Node-based |
| Code Nodes | No | No | Yes (JS/Python) |
| Router/Branching | Advanced | Filters only | Advanced |
| Self-Hosting | No | No | Yes |
| Free Tier | 1,000 ops/mo | 100 tasks/mo | Unlimited (self) |
| Best For | Visual + scale | Simplicity | Code + control |
Pricing
Make uses operations-based pricing — the most cost-effective model at scale. Check the official pricing page for latest rates.
| Plan | Price | Operations/month | Notes |
|---|---|---|---|
| Free | $0 | 1,000 | Testing and learning |
| Core | $9/mo | 10,000 | Individuals and small teams |
| Pro | $16/mo | 10,000+ | Faster execution, priority support |
| Teams | $29+/mo | Custom | Team management, audit logs |
Alternatives to Make
Zapier
Simpler, better for non-coders. Pricier at scale. Best for quick 2–3 app automations.
n8n
More powerful with code nodes; requires DevOps; unlimited executions when self-hosted.
Pabbly Connect
Budget alternative with fewer features. Good for small teams on a tight budget.
Activepieces
Open-source, self-hostable. Newer and growing — worth watching as a free alternative.
Who Should Use Make?
Make is for intermediate automation users who need more power than Zapier but without requiring coding skills.
- + Teams scaling past Zapier: Operations-based pricing saves money as volume grows.
- + Workflows needing branching/routing: Make's routers + iterators beat Zapier's filters.
- + Visual learners: Canvas UI is more intuitive than linear Zap lists.
- - Not for beginners: Zapier has a shorter learning curve.
- - Not for developers: Use n8n if you need inline code.
Make is the sweet spot between Zapier (simplicity) and n8n (power). If you need branching logic or are hitting Zapier's pricing ceiling, Make's visual canvas and operations-based pricing is the next logical step.