Make.com Pricing

How Make.com Pricing Works

Make.com charges per "operation" — one module execution in a scenario. When a scenario runs:

• A 3-module scenario = 3 operations per run
• A 15-module scenario = 15 operations per run
• A 30-module scenario = 30 operations per run

The more complex your scenarios (more modules), the more operations each run consumes. This is a key difference from competitors: a complex multi-step workflow that processes 1,000 events/month could cost 5,000-30,000 operations depending on scenario complexity.

Make.com Plans

Free: 1,000 operations/month, 2 active scenarios, 15-minute scheduling interval. Good for learning.

Core: ~$9/month (billed annually)

• 10,000 operations/month
• Unlimited active scenarios
• 1-minute scheduling interval
• Unlimited users

Pro: ~$16/month (billed annually)

• 10,000 operations/month
• All Core features
• Plus: multi-step scenario creation, full automation history, custom variables, real-time execution

Teams: ~$29/month/seat (billed annually)

• 10,000 operations/month per seat (pooled)
• Team collaboration features
• Shared scenario folders

Enterprise: Custom pricing

• Custom operation limits
• SSO, advanced security
• Priority support, dedicated CSM

Note: operation limits can be increased by buying additional operation packs on top of your plan.

Calculating Your Monthly Operations

Use this formula:

Example 1: Simple alert (3 modules) → 100 times/day = 3 × 3,000 = 9,000 operations/month

Example 2: Complex lead enrichment (12 modules) → 200 new leads/month = 12 × 200 = 2,400 operations/month

Example 3: Email processing (8 modules) → 50 emails/day = 8 × 1,500 = 12,000 operations/month

Add these up across all your scenarios to estimate monthly total.

Comparing Make.com Cost to Zapier

For a 10-step scenario running 1,000 times/month = 10,000 operations/tasks:

Make.com is 15-20x cheaper for the same workflow volume. The gap widens as workflow complexity increases — Make.com's operation count grows with complexity, but so does Zapier's task count, at a much higher per-task cost.

Reducing Operation Usage

If you're hitting plan limits, reduce operations with these techniques:

Filter early: Add filters before expensive modules (API calls, AI processing). If the data doesn't meet criteria, the filter stops execution before consuming operations on those modules.

Consolidate API calls: Instead of three separate modules for three API fields, use one HTTP module that fetches all fields at once. Fewer modules = fewer operations.

Reduce scheduling frequency: A scenario that runs every minute consumes 60x more background operations than one that runs hourly. Use webhooks (instant triggers) instead of polling when the source supports it — webhooks fire only when there's data.

Batch process: Instead of triggering a scenario for each individual event, batch multiple events and process them together with a scheduled scenario. One scenario run processes 50 events at once rather than 50 separate scenario runs.

Archive inactive scenarios: Inactive scenarios don't consume operations, but scenarios that run frequently with no new data (because of polling) waste operations on "nothing to process" runs. Use webhooks instead.

When to Upgrade

Upgrade from Free to Core immediately when:

• You need more than 2 active scenarios
• You need 1-minute scheduling (vs. 15-minute)
• You're running real production automations

Upgrade Core to Pro when:

• You need full execution history for debugging
• You need custom variables (for complex state management)
• You need real-time execution for immediate processing

Recommended Tools

• Make.com — Free tier to start; paid plans from $9/month
• n8n — Self-hosted alternative for very high volumes (pay infrastructure, not operations)
• Claude API — AI calls within Make.com scenarios (separate API cost)
• OpenAI API — Native Make.com integration (separate API cost)
• Airtable — Database that integrates well within Make.com scenarios

“Make.com's operation model rewards well-designed scenarios. Efficient scenarios with good filtering and batching cost significantly less than naive ones.”