Make.com Pricing Guide: Which Plan Is Right for Your Business?

Make.com Pricing Overview

Make.com charges based on operations — executions of individual modules within your Scenarios.

Every time a module executes (trigger fires, an action runs, a filter evaluates with data), that's an operation. A Scenario with 5 modules that runs 100 times = 500 operations.

Current plans (2026 approximate pricing — verify at make.com/pricing):

What Counts as an Operation

Each of these counts as operations:

• Trigger module executing (even if it finds no new data)
• Action module executing (e.g., "Create a contact in HubSpot")
• Filter evaluation (when data reaches a filter)
• Iterator processing each item

Example: Simple lead generation Scenario

• Gmail trigger (1 operation)
• OpenAI (1 operation)
• Router (1 operation)
• HubSpot create contact (1 operation)
• Slack notification (1 operation)

Total: 5 operations per email received. With 200 relevant emails/month: 1,000 operations.

Calculating Your Monthly Operations

Formula:

For polling Scenarios:

Example calculations:

Daily newsletter generation:

• 5 modules × 1 run/day × 30 days = 150 operations/month

CRM lead enrichment (5 modules, runs on each new HubSpot contact):

• 5 modules × 200 new contacts/month = 1,000 operations/month

Email classifier (Gmail polling every 15 min, 5 modules):

• 4 checks/hour × 720 hours = 2,880 checks/month
• IF each check finds 0-2 emails and runs 1 email on average:

- Trigger: 2,880 operations - Other modules: ~800 operations (only runs when email found) - Total: ~3,680 operations/month

Make.com Operations Calculator: Available in the dashboard — enter your Scenario structure and frequency for an estimate.

Optimising Operations

Use webhooks instead of polling: Webhook triggers only fire when data arrives — no wasted operations checking for nothing.

Replace: Gmail "Watch Emails" (polling every 15 min) With: Gmail Pub/Sub integration → Make.com webhook (instant, no polling operations wasted)

Add early filters: If only 10% of emails need processing, add a Filter right after the trigger. Operations are only used for subsequent modules when filter passes. This reduces operations by 90%.

Batch where possible: Instead of processing each record individually (1 trigger + 5 modules per record), batch records and use Iterator:

• Schedule trigger: 1 operation
• Fetch 100 records: 1 operation
• Iterator × 100 (for subsequent modules): 100 operations per module

Depending on the workflow, batching can reduce operations significantly.

Use lower-frequency polling when real-time isn't needed:

• Polling every 15 min: 2,880 trigger ops/month
• Polling every hour: 720 trigger ops/month (75% reduction)

Plan Selection Guide

Free plan (1,000 ops/month): Good for: Testing, very simple single Scenarios, getting started. Not for production use.

Core plan (10,000 ops/month): Good for: Small businesses with a handful of simple Scenarios. Most SMBs handling routine automation.

Pro plan (10,000 ops/month + more features): Same operation count as Core but adds:

• Unlimited team members (Core is 1 user)
• Priority execution
• More advanced features

For teams, Pro is better value.

Teams plan: Per-user pricing; includes 10,000 operations per user. For medium-sized teams.

When to upgrade:

• You consistently hit 80%+ of your operation limit
• You need features only in higher tiers (SSO, custom branding, etc.)
• You need more than the included operation count

Operation add-ons: You can purchase additional operations rather than upgrading plans. Cost-effective if you occasionally go over limit.

Make.com vs Alternatives

Make.com wins on $/operation vs Zapier. n8n self-hosted wins on absolute cost for high-volume.

Recommended Tools

• Make.com — Automation platform (check current pricing)
• n8n — Best for high-volume (self-hosted = free)
• Claude API — AI costs separate from Make.com operations
• Zapier — Compare for your specific use case volume