← Back to all agents
Automation Commercial
Make
Visual automation platform for complex multi-step workflows.
Our take
More powerful and cheaper than Zapier for visual thinkers.
What it is
Make (formerly Integromat) is a visual automation platform. You build "scenarios" by dragging and dropping modules on a canvas, with branching, looping, and error-handling built in. Particularly good for complex multi-step workflows that would be hard to express in linear Zaps.
Best for
- Sync data between SaaS tools with custom logic
- Build complex approval or routing workflows
- Automate e-commerce, marketing, or ops tasks
Pros
- Visual scenario editor is more powerful than linear Zap steps
- Cheaper than Zapier for high-volume workflows
- Strong API support — can connect to anything with HTTP
Cons
- No self-host — pure cloud
- UI can feel complex to first-time users
Quick start
- Sign up at make.com — Free tier gives 1,000 ops/month (~10 simple scenarios).
- Click "Create a new scenario" → drag the first app's module onto the canvas → connect apps with bubbles + lines (visual flow).
- Choose scenario type: Scheduled, Instant (webhook), or App-event triggered.
- Add modules: data transforms (filter, router, iterator), AI via the "OpenAI" module or HTTP-callable text generation.
- Test step-by-step ("Run Once") → schedule → enable.
- Pricing: Core $9/mo (10k ops); Pro $16/mo (10k+); Teams $29/mo; Enterprise custom. Operations = actions, not runs.
Sample input / output
Input
Scenario: "Stripe → NetSuite Monthly Close Sync"
Trigger: Schedule, 1st of the month at 02:00 UTC
Modules (12 total):
1. Stripe: list_charges(date_window)
2. Filter (amount > 0; status = "succeeded")
3. Iterator (process each charge)
4. HTTP: Get customer info from Salesforce by Stripe customer ID
5. NetSuite: search_transactions_external_id
6. Router:
- Branch A: no match → NetSuite create_invoice
- Branch B: match → NetSuite update_invoice
7. Aggregator (group by customer)
8. Error handler module: Slack #finance-ops alert on failures
9. Set variable (count of sync successes / failures)
10. Gmail: email [email protected] with monthly summary
Error tolerance: max retries = 3, pause on error. Output
Run on 2026-07-01 02:00 UTC:
- Stripe charges processed: 4,820
- Filtered to succeeded: 4,801
- Created invoices in NetSuite: 142
- Updated existing invoices: 4,659
- Failed: 19 (all sandboxed in error handler; Slack alert dispatched, finance team triaged manually)
- Total ops used: ~14,460 (would have exceeded 10k Core cap; needs Pro or Teams at this volume)
Compared with manual monthly close: 4 days → 30 minutes + 1 hour of failure triage. Benchmarks
Plans Free; Core $9/mo; Pro $16/mo; Teams $29/mo; Enterprise custom — Make pricing 2026
Integrations 1,500+ apps + HTTP / Webhook / SMTP for anything else — Make integration directory
Visual canvas Drag-drop modules with full branching / loops / error handling — Make product
Free ops tier 1,000 ops / month — Make pricing 2026
API Public REST API + scenario webhooks for custom integration — Make docs
Pricing
Free tier; Core $9/mo
Underlying models
Should you pick this?
Pick it if You build complex multi-step automations with branching / loops / error handling and prefer a visual canvas over Zapier's linear step list. Cheaper than Zapier at high volumes.
Skip it if Your automations are simple one-shots (Zapier wins for non-technical setup + simple flows), or you need self-hosting (n8n is the default). For pure AI agents without visual flow, try Lindy or Zapier Agents.