Every Make.com limit, by plan

Make (formerly Integromat) bills in credits, which replaced operations as the billing unit, and most other limits scale with the plan or with the credits you license. As of November 2026, the Free plan includes 1,000 credits a month, a 15-minute minimum interval between scheduled runs, a 5 MB maximum file size, and a much shorter maximum scenario run than paid plans. Paid plans (Core, Pro, Teams, Enterprise) can schedule every minute and process larger files: 100 MB on Core, 250 MB on Pro, 500 MB on Teams and 1,000 MB on Enterprise.

Several allowances are tied to licensed credits rather than to the plan name. For every 10,000 credits per month you get 5 GB of data transfer, 10 MB of data storage, 10 MB of incomplete-execution storage (2 GB maximum), and 667 webhook queue items (10,000 maximum). Running out of credits is a fatal error: Make disables the scenario's scheduling immediately.

One discrepancy to know about: Make's pricing table lists a maximum scenario execution time of 40 minutes (5 minutes on Free), while the help center's error reference says a scenario is interrupted after 45 minutes (10 minutes on Free). Both are documented below. Values are from make.com/pricing, the Make Help Center, Make Academy and the Make API docs, verified November 12, 2026. Prices and plan limits change often.

The plan sets the scheduling floor, the file-size ceiling and the run-time ceiling. Credits are bought in tiers on top of the plan. Free has a fixed 1,000 credits, and paid plans let you pick a monthly credit volume on the pricing page. Core, Pro and Teams can turn on extra-credit auto-purchasing, which buys 10,000 credits when the balance runs out. Extra credits expire after one month on monthly plans, or at the end of the year on annual Pro and Teams subscriptions.

Make sizes several storage and transfer limits by licensed credits per month rather than by plan. A 150,000-credit subscription therefore gets 75 GB of data transfer and 150 MB of data storage. Data stores take at least 1 MB each, and an organization can have up to 1,000 of them. A single data store record can be up to 15 MB. When storage runs out, data store modules output an OutOfSpaceError.

Individual modules wait a limited time for third-party apps. Most Make modules have a 40- or 60-second runtime limit, and Airtable has an extended timeout of up to 80 seconds. Webhooks have their own response codes for a full queue or a rate-limit hit, and webhooks not attached to any scenario are switched off after five days. The Make API, used to manage scenarios programmatically, has per-plan request limits.

Out of credits: modules output OperationsLimitExceededError. Make treats it as fatal and immediately disables the scenario's scheduling, regardless of the consecutive-errors setting.

Run too long: the active module outputs ExecutionInterruptedError. The run ends with a warning and remaining bundles aren't processed, but Make keeps scheduling future runs.

File too big: MaxFileSizeExceededError. If it happens in the trigger, Make deactivates the scenario immediately; on later modules it never deactivates.

Third-party rate limit: RateLimitError (HTTP 429). For scheduled scenarios Make pauses scheduling for 20 minutes.

Storage full: OutOfSpaceError. Slow app: ModuleTimeoutError - The Operation timed out. Make API: 429 Requests limit for organization exceeded, please try again later.

Split long scenarios. Make's own fix for ExecutionInterruptedError is to break the work into smaller scenarios, for example one that queues items and another that processes a limited batch per run.

Spend fewer credits. Use instant (webhook) triggers instead of frequent polling, put filters before expensive modules, and use aggregators to write many bundles in one call.

Handle errors explicitly. Add Retry or Break error handlers and enable incomplete executions so failed runs are stored and retried instead of lost.

Compress or split files that exceed your plan's file-size limit.

Buy extra credits or upgrade when credits run out. Auto-purchasing on Core, Pro and Teams prevents a fatal stop. Higher plans raise file size and API limits.