Make (Integromat)
Automation with branches, loops, and shape.
Make (rebranded from Integromat) is a visual automation platform where you draw the workflow as a node graph — routers branching, iterators looping, aggregators combining. More thinking than Zapier, more capability too. And for high-volume work, dramatically cheaper per operation.
Make scenario · Order processing workflow
Tracing: New customer path
Webhook· Order created
Step 1 / 4
Non-linear. Routers split data; Iterators loop; Aggregators combine. The real toolset for complex workflows.
Where Make pulls ahead
The scenarios Make handles better than Zapier.
Branching workflows
Order in → route by type (digital / physical / subscription) to three different downstream flows. Make's Router module is native; Zapier's Paths feel bolted-on.
Loops over arrays
"For each item in this list, do X" — Make's Iterator + Aggregator pair is first-class. Processes a CSV upload's 100 rows in one scenario run, not 100.
Aggregating data
Combine results from multiple API calls into one payload. Branch out, do 3 things in parallel, combine results at the end. Native pattern.
Complex transformations
Built-in functions for string/array/math operations. JSON reshaping without 6 chained Formatter steps. Custom JavaScript snippets available too.
High-volume automation
Operations-based pricing (vs Zapier's tasks) is cheaper at volume. Scenario with 1 complex run = 10-15 ops; equivalent in Zapier = 10-15 tasks. Make's price per op is typically 30-50% lower.
Scheduled + batched workflows
"Every morning 6am, pull yesterday's orders, group by customer, email daily summary". Make's scheduling + aggregation handles this natively.
The module palette
The tools modules that give Make its power.
Beyond app connectors, Make has "tools" modules — the logic primitives you drop between connectors to shape workflows. Knowing these is the difference between basic automation and real pipelines.
Router
Split flow into multiple branches, each with its own filters. Native branching.
Iterator
Take an array, process each item as its own mini-flow. "For each row in CSV".
Array Aggregator
Combine items back into an array after iteration. Used with Iterator.
Numeric Aggregator
Sum / avg / min / max / count across iterations. Running totals, KPI calcs.
Text Aggregator
Concatenate text across iterations. Build long emails from multiple records.
Tools → Set Variable
Store computed values for reuse later in scenario. Like local variables in code.
HTTP
Make any REST API call to any endpoint. The universal escape hatch.
Webhook
Custom webhook endpoint to receive external events. Instant triggers.
Error Handler
Rollback, Ignore, Resume, Break — define per-module what happens on failure.
Ops pricing, explained
How Make's operations pricing works (and wins at volume).
Make counts "operations" (each module execution). Zapier counts "tasks" (each action run). For most real workflows, Make's pricing is 30-50% cheaper per unit of work.
Free
€0/mo
1,000 ops/mo
2 scenarios
Every 15 min min interval
Trial / solo low-volume
Core
€9/mo
10,000 ops/mo
Unlimited scenarios
Every 1 min interval
Solo operators + SMBs
Pro
€16/mo
10,000 ops/mo
+ custom variables + priority
Every 1 min
Mid-complexity SMB
Teams
€29/mo
10,000 ops/mo
+ team features + SSO
Every 1 min
5+ person orgs
Worked example — same workflow on both platforms: A webhook triggered 1,000×/day running 5 modules each = 5,000 ops/day = 150,000 ops/mo. On Make: ~€30/mo with Teams + overage. On Zapier Professional: would be 150,000 tasks at ~€450/mo. Make wins by 3-4× at this volume.
The ceiling
Where Make isn't the right answer.
Non-technical marketer trying to self-serve
Make's learning curve is real. Routers, Iterators, Aggregators are logical but need hours of tutorial. Zapier fits solo marketers better — Make needs someone comfortable with data structures.
Need a super-obscure app integration
Make has ~1,500 native apps vs Zapier's 7,000. For popular apps: parity. For niche apps: Zapier more likely to have a native integration. Fall back to HTTP module if needed.
Simple single-step workflows
If the workflow is "Gmail → Slack", Make adds unnecessary complexity. Zapier's simpler model fits linear flows better. Use right tool for right shape.
Real-time sub-second requirements
Make's minimum interval is 1 minute for scheduled triggers (instant for webhooks). For true real-time, write code against the APIs directly.
Extreme compliance / audit trails
Basic execution logs exist. For regulated industries needing immutable audit trails, version control, formal change management — write custom code with full CI/CD.
Scenarios >50 modules
Scenario canvas becomes unwieldy past 50 modules. Split into multiple scenarios that call each other via webhooks. Or consider custom code for the complexity.
Frequently asked
Make questions.
Zapier for simple linear flows + non-technical owners. Make for branching/looping/aggregation + someone willing to learn the model. Many teams use both: simple flows on Zapier (speed), complex + high-volume on Make (cost + power).
Related
Related automation tools
Got a complex workflow to automate?
45-minute scoping call. Describe the flow — branches, loops, volumes. We'll sketch the scenario, estimate ops, compare against Zapier and custom code. You'll know the right answer before committing.