Make Automation Your scenario switched off. Enquiries stopped.
We build and watch Make scenarios.We build and watch your Make scenarios, so you stop opening Make each morning to check it’s still on.
- Every scenario watched for failed steps
- Fewer credits spent on empty checks
- Built in your own Make account
Scenario switched offWebsite enquiries to the CRM
Where credits go
Empty checks cost credits. We cut them.
A scenario on Make’s default timer checks 96 times a day. Each check costs a credit, enquiry or no enquiry.
96 credits a day
93 found nothing
3 credits a day
Starts only when the app sends the enquiry (a webhook).
Example: one day, three enquiries, counting only the step that starts the scenario. Make charges for every check, found or not: each check is one operation, and one operation is one credit for non-AI apps (Make help centre: operations, credits, checked 17 Nov 2026). Later steps cost the same either way.
Paying for empty checks? Tell us which scenario.
Get StartedOut of credits
One scenario used them up. All of them stopped.
When the month’s credits run out, Make pauses every scenario in the account, busy or quiet.
This month’s credits
- Website enquiriesOff
- Invoice remindersOff
- Weekly reportOff
- Welcome emailOff
- Quote follow-upOff
- Stock alertOff
Out of credits, every scenario in the account pauses, and data sent to a webhook waits in Make’s queue (Make community help post, May 2024). Extra credits cost 25% more than the credits in your plan (Make help centre, checked 17 Nov 2026).
Credit budget
Every scenario on one sheet.
How often each one runs, what it spends a month and who owns it. The biggest spender shows at once.
Credit budget
| Scenario | How often | Owner | Credits a month |
|---|---|---|---|
| Website enquiries | Every 15 min | Sales | 2,880 |
| Stock alert | Every hour | Operations | 720 |
| Quote follow-up | On arrival | Sales | 120 |
| Welcome email | On arrival | Operations | 90 |
| Invoice reminders | Weekdays, 9:00 | Accounts | 22 |
| Weekly report | Mondays, 8:00 | Accounts | 4 |
| Total a month | 3,836 | ||
Counting only the step that starts each scenario, as in the squares above.
Example figures, not a client’s account.
Biggest spender. Fix it first.
Easy to follow
Every step named on one screen.
A scenario only its builder can read becomes a problem the day they leave.
Webhooks · Custom webhookNew enquiryText parser · Match patternSpam out- Same name twice. Which is which?
HTTP · Make a requestFind the customer HTTP · Make a requestUpdate the CRMEmail · Send an emailTell sales
Plain names. Every step says what it does, in words your team already uses.
Your team
The people in your Make account.
An engineer for the connections, a developer for the scenarios.

A dedicated account manager.
One person who knows your business and owns the work.

Workflow developer.
Builds scenarios that are easy to follow, and keeps running costs down.
- 1We review your details.
- 2We talk it through with you.
- 3We propose a solution.
- The systems, the code and the accounts are yours.
- An in-house AI team, working as part of yours. We cover operations, visibility, websites and growth with one team.
- Priority access to Luna. Partners go to the front of the queue with our AI assistant.
- We accept only a limited number of partnerships each quarter.
Questions
Make’s credits and switch-offs, answered.
Make’s own rules, linked, and what we do about each.
What is Make automation?
Make (make.com) is a visual automation tool. Each automation, which Make calls a scenario, is a row of steps that moves information between apps such as a website form, a CRM and email. SuperToasty’s Make Automation service builds those scenarios in the client’s own Make account, then watches and fixes them after launch.
Make Automation includes:
- A map of your work today
- Every step named
- A route for failed steps
- Tests on real work
- Watching and fixes after launch
Make Automation suits a business whose Make scenarios:
- keep switching off
- use more credits than expected
- were built by someone who has left
What does a Make automation agency do?
A Make automation agency builds and looks after the scenarios that move information between your apps. At SuperToasty that includes a map of how the work runs today, scenarios with every step named in plain words, a route for failed steps, tests with your team on real work, and monitoring and fixes after launch. One account manager stays with you throughout.
Is Make free?
Make has a Free plan with 1,000 credits a month. Paid plans, such as Core, Pro and Teams, come with more (Make’s pricing page, checked 17 Nov 2026). On Make’s default 15-minute timer, one scenario spends 96 credits a day on checks alone, about 2,880 in a 30-day month: more than the Free plan holds. Make runs on your own account, so you can see what it costs.
Why does my Make scenario keep getting deactivated?
Make switches a scenario off at its first error if it starts the moment data arrives, and after three errors in a row if it runs on a timer (Make help centre, checked 17 Nov 2026). Nothing runs until someone turns it back on. We give failed steps their own route, and watch every scenario after launch.
Why is Make using credits when nothing happened?
Make charges a credit each time a scenario on a timer checks an app for new data, even when it finds nothing: each check is one operation, and one operation is one credit for non-AI apps. By default a scenario runs every 15 minutes (Make help centre: operations, credits, schedules, checked 17 Nov 2026). That is 96 checks a day, about 2,880 credits in a 30-day month, before any real work. With a webhook, the app tells Make the moment something arrives, and the scenario runs only then. Our workflow developer keeps running costs down by using each tool well.
What happens when Make runs out of credits?
A Make account that runs out of credits pauses every scenario in it, busy or quiet, and data sent to a webhook waits in Make’s queue until credits return (Make community help post, May 2024). With automatic top-ups on, Make buys 10,000 extra credits at a time instead, at 25% more than the credits in your plan (Make help centre, checked 17 Nov 2026). We find which scenario spends the most, and fix that one first.
Can you fix Make scenarios someone else built?
Yes. SuperToasty takes on Make scenarios someone else built. We read each one before we change anything: its run history, its credit use and the app logins it depends on. The ones that carry your enquiries and orders come first, and everything stays in your own Make account.
Should we move from Zapier to Make?
Zapier is quickest for simple links between popular apps, so a two-app link can stay there. Make suits visual, multi-step workflows: several steps, branches and lookups you can follow on one screen. When your Zaps have grown into that, we rebuild them in your own Make account and test them with your team on real work before you switch. Hosting it yourself is a job for n8n.
Keep going
Not quite what you need?
Everything we automate in one place, or the service closest to this one.
