Before paying for Make: map one workflow and its credit use

Start with one recurring task you can describe precisely. Write down what starts it, which records it processes, and what a successful result looks like. This gives you a small workflow to evaluate before choosing a paid plan.

Decide whether automation solves the problem

For a marketing team, first separate two questions: do you need a clearer place to manage customer records, or do you need to move those records between existing apps? If both apply, define the records and ownership before automating the transfer. If the task is occasional and your current tools handle it reliably, keeping the manual process is a valid outcome. This is a planning framework, not a claim that one product replaces every role.

A worksheet for the first workflow

Question	Your answer should identify
What starts the task?	A specific event or a scheduled check
What changes?	The records to read, transform and write
Where does it finish?	The destination app and expected output
How quickly is it needed?	An acceptable delay, rather than “real time” by default
How will you detect a problem?	A missing result, duplicate or error to inspect

Use non-sensitive sample records for your first evaluation. Check whether the exact app action you need is available; a service appearing in an app directory does not answer every question about a particular workflow.

What the current Free plan tells you

At our source check on 13 September 2026, Make’s pricing page listed a Free plan at $0 with up to 1,000 credits per month and a 15-minute minimum interval for scheduled runs. It explains that most module actions consume one credit, while some advanced features can consume more. These are plan constraints, not a promise that every workflow will fit. Make pricing and credit explanation

Estimate, then compare with a real run

For illustration, assume a workflow executes three chargeable one-credit actions for each record. At 200 records per month, that simple model is 3 × 200 = 600 credits. The arithmetic is a planning example. Polling, retries, branching, extra records or differently charged modules can change actual consumption.

Write down the usage assumption beside each step. Run a small authorized example in your own workspace and compare the recorded consumption with your estimate before scaling it.

If the required schedule, available actions or measured consumption do not fit, first check whether a simpler workflow, a less frequent schedule or your existing tools would meet the need. Compare a paid configuration only if that remaining need justifies it. Record its billing period, included credits, overage choices and team requirements together. An annual price displayed per month is not necessarily a monthly payment option.

This fieldnote does not recommend a paid plan or quote a verified team-wide cost. We have not tested your workflow. It contains ordinary source links and no affiliate purchase links.