Make Credit Spend Controls Checklist

Look forAnnual billing saves about 25% for US buyers, so monthly billing costs about a third more than annual. Annual Pro and Teams allocate the full year's credits up front, which covers seasonal peaks. Core allocates monthly even on annual billing, and its extra credits expire at each monthly reset.

Look forUse instant webhooks where the app offers them, because they run only when data arrives. Polling consumes a credit on every check. GILD calculates about 43,200 checks per 30-day month at one-minute intervals and 2,880 at 15-minute intervals. A user's Asana trigger checked every 3 minutes and used credits overnight without new activity.

Look forCount bundles per module. After an iterator over 100 rows, one module uses 100 credits per run. Aggregate first or use bulk modules to reduce operations. Routers and error handlers use none. One team moved file IDs into custom variables updated twice a month after 20 scenarios spent 60,000 monthly operations on repeated lookups.

Look forDecide whether to stop at the allowance. Without credits, scenarios stop and webhooks queue up to the plan's queue size. Extra credits cost 25% more, in manual units of 1,000 or automatic batches of 10,000. Auto-purchase stops at the plan's credit count. Enterprise adds overage protection. Core extra credits expire monthly. One user lost 10,000 credits bought two hours before reset.

Look forSet monthly or yearly limits per member in private spaces on any plan. Enterprise team limits pause scenarios at the limit and send emails at 75%, 90%, and 100%. Use its analytics dashboard to rank scenarios by operations.

Look forChoose who bills tokens. Since August 25, 2026, Make's Small and Medium tiers charge one credit per 18,080 input or 2,260 output tokens. Large charges per 3,616 input or 452 output tokens. A custom provider connection on a paid plan bills operations only. The Code app costs 2 credits per second.