Your Make scenario got big. Now nobody wants to open it.

We are not the people to rebuild it

Gonzo does not do Make building, and our systems are Python agents. If you found this page while looking for Make help, you should still get something useful: a way to tell whether your scenario is fine or has turned into a liability.

Keep it

A scenario can stay as it is when all of these hold:

• It moves data between your own tools.
• A failure shows up for you the same day.
• You can say in one sentence what each branch does.
• It never replies to a customer.

Replace it

Rebuild the scenario, or split it, when any of these is true:

• A router sends customers different messages depending on conditions you can no longer list.
• It sends WhatsApp messages, and nobody has written down what it does outside the 24-hour reply window or after someone opts out.
• It handles anything that looks like money.
• Handing it to someone else would take a day of explanation.

Rebuilding does not have to mean us. A cleaner scenario, or two small ones, may be the answer, and the usual first step is to separate the part that moves data from the part that talks to customers.

Counting credits

Credits a month come to roughly runs a month times actions per run, as long as most actions use one credit. A scenario with 6 actions that runs 1,000 times a month uses about 6,000 credits. That is above the 5,000 on the entry paid plan, so you would need a bigger plan or fewer steps. The figures are an example, not a forecast for your scenario. Open your own scenario history and count.

Make's prices as read on October 2, 2026

Make's pricing page shows a free plan with up to 1,000 credits a month, and paid plans starting at $9 a month for 5,000 credits. Most actions use one credit.^[1] Plans are labeled differently in different views of that page, so we quote only the free tier and the entry paid price.^[1]