Make
Tool · this deep dive is built from the official pages of the platform itself and of the tools that support it.
Overview
Make is an automation service: one service learns of an event, another responds to it, and between them sits a scenario assembled without programming. In this guide it belongs to automation: it publishes nothing itself, but it can publish for you wherever the platform offers programmatic access.
Pricing is published on an open page, and the important part is not the sum but the unit of account. You pay not for platforms or accounts but for operations: every step of a scenario spends one.
Who is here
The pricing page gives no audience figures.
Getting started
A free tier exists and lets you try the service properly: up to 1,000 operations a month and two active scenarios.
But it carries a limit that matters more than the operation count: the minimum interval between runs is fifteen minutes. A scenario will not fire more often, however many operations remain. For work that needs an immediate response — replying to a message, picking up an order — the free tier does not fit by design, not by volume.
What you can publish
Not applicable: Make is not a platform but an intermediary between platforms. What may be published is decided by the platform you publish to.
How to grow
Not applicable for the same reason.
The road to monetisation
Not applicable: the service does not pay creators; it is paid.
Tools and automation
Four named plans plus one by agreement:
- Free — 1,000 operations a month, 2 scenarios, 15-minute interval;
- Core — 9 USD a month for 10,000 operations;
- Pro — 16 USD for the same volume;
- Teams — 29 USD for the same volume;
- Enterprise — price by agreement, operation volume not stated on the page.
This is worth pausing on: Core, Pro and Teams differ not in volume but in capability. All three are quoted for the same 10,000 operations. Comparing them by price per operation is pointless — the price per operation is identical; what differs is everything else.
On all paid plans the minimum interval between runs is one minute, and the number of active scenarios is unlimited.
Limits and rules
The fifteen-minute interval on the free tier is the only frequency limit named on the pricing page.
Who it suits
Make suits someone who wants to connect several services and is willing to count operations: the spend is predictable and the price is quoted per an understandable unit.
The free tier suits testing an idea, but not work where a response is needed sooner than fifteen minutes.
Choosing between Core, Pro and Teams, look not at volume — it is the same — but at what you find missing in the cheaper one.
Verified data
The checked data this deep dive rests on.
Pricing
there is a free plan: up to 1,000 operations («credits») a month, 2 active scenarios, minimum interval between runs of 15 minutes
The fifteen-minute interval is the main limitation of the free plan: the scenario will not run more often, however many operations are left
source, checked 2026-08-11
9 USD a month for the Core plan (10,000 operations); Pro 16 USD, Teams 29 USD for the same volume
The prices are given for the same volume of 10,000 operations: the difference between plans is not in volume but in features
source, checked 2026-08-11
four named plans — Free, Core, Pro, Teams — and Enterprise at an agreed price
The page does not name the operation volume for Enterprise
source, checked 2026-08-11
Limits and restrictions
on paid plans the minimum interval between scenario runs is 1 minute and the number of active scenarios is unlimited
source, checked 2026-08-11
Catalogue section: all similar See also: catalogue index · scheduler comparison · find by situation · platform restrictions