What Make documented about the Integromat shutdown
Make publishes a notice about the change on its own site. It calls Integromat "a legacy product offering" and says "support will end for Integromat in 2023." It also says all existing customers would have the opportunity to "seamlessly upgrade to Make over the course of the next year" while "paying the same prices that they currently pay," and that new users "will be redirected now to the Make platform for registration." [1]
The notice does not give a day or month for the end of support, and it does not describe a migration tool or what happened to individual scenarios, data stores or connections. Treat any blog post that promises a specific migration procedure as unverified unless it links to Make's own documentation. [1]
What changed for legacy users: operations became credits
Old Integromat tutorials talk about operations, because that was the billing unit. Make now bills in credits. Its pricing FAQ says "As of August 27, credits are the billing unit in Make," and its credits article says "Credits replaced operations as the term for Make's billing unit" and that existing plan pricing, including the cost of credits, remained unchanged. [4] [2]
Operations still exist as a measure of activity. Make defines an operation as "a single module run to process data or check for new data." For non-AI apps, and for third-party AI apps such as OpenAI, one operation equals one credit. Some built-in Make AI modules use more: Make's example shows modules consuming 2 or 10 credits per operation. [3] [2]
| Term in an old tutorial | What to check on Make today |
|---|---|
| Operations as the billing unit | Credits are billed; 1 operation = 1 credit for non-AI apps [2] |
| A free plan allowance quoted in operations | Free plan: 1,000 credits a month, 1 data store, 1 MB data storage [4] |
| AI steps priced like any module | Make AI features may use more than 1 credit per operation [2] |
| Router or error handler adds cost | Router and error handler modules use no credits [4] |
How usage is counted
Make's operations article says a trigger runs once each time it checks for or retrieves data, regardless of how many bundles it returns, while every later module runs once per bundle. In its example, a trigger returns 10 form responses and three later modules each run 10 times, for 1 + 30 = 31 operations. [3]
Running out matters more than it did in many old tutorials' screenshots. Make's pricing FAQ says that when credits run out, scenarios stop until credits are added; webhooks queue up to your queue limit, and polling scenarios resume from their last successful run. Extra credits come in bundles of 1,000 or 10,000 and expire one month after purchase on monthly plans. [4]
Worked example: an old tutorial on the free plan
Say an Integromat-era tutorial shows a scenario that polls a spreadsheet every 15 minutes and sends an email for each new row. Polling every 15 minutes is 4 checks an hour, 96 a day and 2,880 in a 30-day month. Because a trigger counts each check as one operation, the checks alone use 2,880 credits before any row is processed, nearly three times the free plan's 1,000 credits. [3] [4]
Add 50 new rows in the month and each one runs the email module once, for 50 more credits. The fix is not the email step but the schedule: checking once an hour cuts the checks to 720 a month, and an instant webhook trigger is worth considering if the source app supports one. Confirm actual use in the scenario's run history before changing plans.
Checklist for anyone following an Integromat tutorial
- Translate every operation count in the tutorial into credits, and look for AI modules that may cost more than 1 credit each. [2]
- Recalculate trigger checks from your schedule: one operation per check. [3]
- Ignore plan prices and allowances in old screenshots; read Make's current pricing page. [4]
- Keep routers and error handlers where they help, since they use no credits. [4]
- On the free plan, plan around a single data store and 1 MB of storage. [4]
- For webhook scenarios, check the queue: Make allows 667 queued webhooks per 10,000 licensed credits, up to 10,000. [4]
- Replace old Integromat links and product names in your own documentation with links to Make's current help pages.
Who should act now
- Anyone budgeting from an Integromat-era article: recount in credits before you choose a plan.
- Teams adding AI steps to old scenarios: check the credit tag on each Make AI module first. [2]
- Free-plan users with frequent polling: lengthen the interval or switch to an instant trigger.
- Skip a rebuild if your scenario already runs on Make and its history shows credit use inside your plan.
Questions before you decide
Is Integromat still available?
No. Make's notice describes Integromat as a legacy product and says support for it ended in 2023, with new users redirected to register on Make.
Did Integromat customers pay more after moving to Make?
Make's notice said existing customers could upgrade to Make while paying the same prices they currently paid. It does not give later price guarantees, so check your current plan on Make's pricing page.
What is the difference between operations and credits?
An operation is a single module run to process data or check for new data. Credits are the billing currency. For non-AI apps one operation costs one credit, while some Make AI features can cost more.
Do routers and error handlers cost credits?
Make's pricing FAQ says the Router and the error handler modules Rollback, Break, Resume, Commit and Ignore do not consume credits.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make: Integromat shutdown notice Accessed 30 Oct 2026
- Make Help Center: Credits Accessed 30 Oct 2026
- Make Help Center: Operations Accessed 30 Oct 2026
- Make pricing and billing FAQ Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.