Automation · by Make (Celonis)
Make
Make (formerly Integromat) lets you build automations on a visual canvas, with routers for branching, iterators for loops, error handlers and data stores. It suits more complex flows than simple trigger-action tools and is usually cheaper per step at volume. Since 2025 Make bills in credits: most module actions use one credit, and some AI and code features use more. Paid plans (Core, Pro, Teams) are priced by credit tier; Enterprise is custom.
- Paid plans from
- $9/mo
- Free plan
- Yes
- Data portability
- moderate
- Last reviewed
- Oct 13, 2026
Plans & pricing
Credits are the billing unit: most module actions use 1 credit; some AI features and Make Code (2 credits per second of execution) use more. Since 6 November 2025, extra credits (automatic or manual) cost 25% more than plan credits, and Core is capped at 300,000 credits/month. Annual billing is cheaper than monthly. A Start-up Plan offers 50% off for companies under 20 employees.
| Plan | Price (USD) | Highlights | Evidence |
|---|---|---|---|
| Free | $0/mo |
| Verified· Oct 13, 2026Source |
| Core | $9/mo billed annually · Entry tier with 10,000 credits/month: $9/month billed annually, $10.59 billed monthly. |
| Verified· Oct 13, 2026Source |
| Pro | $16/mo billed annually · Entry tier with 10,000 credits/month: $16/month billed annually, $18.82 billed monthly. |
| Verified· Oct 13, 2026Source |
| Teams | $29/mo billed annually · Entry tier with 10,000 credits/month: $29/month billed annually, $34.12 billed monthly. |
| Verified· Oct 13, 2026Source |
| Enterprise | Not listed Custom pricing. |
| Verified· Oct 13, 2026Source |
What Make does
4 capabilities mapped. Click one to compare every tool that does it.
| Capability | Fit | Quality | Ease | Precision | Team | Plans | Watch out for |
|---|---|---|---|---|---|---|---|
| Automate simple app-to-app workflows | Core feature | — | All plans | Steeper learning curve than Zapier for simple tasks · Free plan has only 1,000 credits | |||
| Run multi-step, high-volume automations | Core feature | — | All plans | Very large scenarios become hard to maintain · Code execution consumes extra credits | |||
| Run AI agents that complete multi-step tasks | Partial | — | — | All plans | AI features can use more than one credit per step · Plan-level agent limits not confirmed this session | ||
| Store structured data in a shared database or spreadsheet | Workaround | — | — | All plans | Storage is small (10 MB per 10,000 credits); not a team database |
Fit and scores (1–5) are editorial judgements. How we score
Why people pay for it
- A visual canvas that shows complex multi-branch automations clearly.
- Lower cost per step than Zapier for high-volume flows (editorial view).
- Routers, iterators, aggregators and error handlers for real data processing.
- A large app library (the pricing page cites 3,000+ apps) plus HTTP and webhooks for anything else.
- Hosted: no servers to run.
Reasons to keep paying
The honest case for Make. If these matter to you, don't switch.
- Complex scenarios with branching and error handling that took real effort to build and debug.
- Hosted reliability without the overhead of self-hosting an automation server.
- A balance of power and no-code usability that sits between Zapier and developer tools.
Risks to know about
- mediumvendor lock in
Blueprints only work in Make; moving platforms means rebuilding scenarios.
- lowreliability
Scenarios pause when credits run out unless auto-purchase is on (at a 25% premium).
- mediumsensitive data
Data passes through Make's cloud and execution logs; review retention for sensitive data.
- data portability: moderate
Scenarios export as JSON blueprints that can be re-imported into Make, but not into other platforms. Data stores export to CSV.
Overlaps with
Tools that share capabilities with this one — the first place to look for duplicate spend.
Sources & freshness
- Make pricing — accessed Oct 13, 2026
- Make Help Center: adjustments to plans and pricing — accessed Oct 13, 2026