Is Make Free enough for your workflow?

Make Free can be enough for a small recurring task. Use this worksheet to decide whether your task fits, needs measurement, or exceeds its limits. You can make the first estimate without an account.

We may earn a commission on qualifying paid Make subscriptions through links in this guide. A Free signup alone does not earn us a commission.

A scenario is a workflow; a module is a step in it. One run can use several credits. Your budget needs to include checks, testing and repeat runs.

1. Check the limits before counting credits

Make's Free plan (opens in a new tab) currently includes:

• 1,000 credits per month
• Two active scenarios
• A minimum scheduled interval of 15 minutes
• A maximum execution time of five minutes
• A maximum file size of 5 MB
• 512 MB of data transfer per monthly allowance period
• Seven days of execution-log storage

Note how many scenarios must stay active and how long an item can wait. Check file limits where relevant and save trial notes before old logs disappear.

The 15-minute limit concerns scheduled runs. Some triggers support an immediate response to an incoming event (opens in a new tab). Check the specific integration before treating that as an alternative. An instant trigger still has credit usage and service limits.

If your source only supports polling and you must check it every five minutes, Free does not fit that requirement. A low item count does not change the scheduling limit.

2. Fill in your monthly budget

Use your Make organization's allowance dates. Label an assumed period, such as 30 days; a 31-day period needs a different check count. Copy this worksheet:

Add your workflow estimate, other scenarios' credits, setup and repeat-run credits, and chosen reserve. Subtract that total from 1,000. Partway through the period, include credits already spent and forecast only the remaining work. Do not count a trial or trigger twice.

What belongs in the candidate projection?

Most fixed-rate modules use one credit per operation (opens in a new tab), with exceptions. Some AI and advanced features charge by tokens, pages, file size or run time. Use the module's rules and displayed credits, not the number of boxes on the canvas.

Operations depend on the bundles processed (opens in a new tab). A bundle is one unit of data. A trigger can return several bundles, each causing later work. Record branches and rejected items too.

For polling, include checks that find nothing. Make's scheduling example (opens in a new tab) budgets 720 trigger credits for hourly checks across 30 days in its Google Sheets example, before downstream actions. That is a documented example, not a measured price for your scenario. Record an empty check and a check with data in your own trial before using a polling rate in your budget.

For variable costs, test small and large inputs and keep a range until you can choose an upper estimate. Unknown cost means needs measurement. Connected apps or AI providers may charge separately; a Make budget does not cover those fees.

3. Use the result to choose your next step

Filled example: a daily workflow with room to test

This is a fictional completed budget to show the decision. Its usage figures are illustrative inputs, not results from a HoldMyTwist integration test or module prices to copy.

The reader wants a daily list of new item records. They can wait a day, need one active scenario and expect 100 records across 30 days. No files are processed. Assume their task passes the remaining limits.

For this arithmetic example, assume the work done once per daily check, including the trigger, uses two credits. Processing each record uses another three credits. The candidate projection is 30 checks × 2 credits + 100 records × 3 credits = 360 credits. Use your own trial's credits and execution counts, listing extra branches or batch steps separately.

• Candidate scenario projection: 360 credits
• Other scenario usage: 120 credits
• Setup tests and repeat runs: 40 credits
• Reader-chosen reserve: 200 credits
• Total budget: 360 + 120 + 40 + 200 = 720 credits
• Remaining allowance: 1,000 − 720 = 280 credits

Decision: fits under these assumptions, with 280 credits left after the reserve. This does not promise capacity for another workflow. Your own fit decision needs trial evidence covering empty checks and busy periods. Otherwise, mark it needs measurement.

Boundary example: 920 credits is not automatically a fit

Suppose your candidate projection is 920 credits. You also expect 60 credits elsewhere and choose a 100-credit reserve for tests and variation. The total is 1,080 credits, which exceeds the allowance by 80.

Decision: does not fit that budget. These are hypothetical inputs, not tested costs. Reduce the work, change an acceptable schedule, or compare a paid plan. Do not remove a needed reserve just to make the sum pass.

Record your decision

• Fits: the plan limits work for your task, your representative measurements support the projection, and the total including your reserve stays within the allowance.
• Needs measurement: a credit rate, empty check, busy batch, required feature or other scenario's usage is unknown. Name the missing test before deciding.
• Does not fit: a required limit fails or the completed budget exceeds the allowance. Change the requirement or compare another option.

A spreadsheet or calculator handles this budget. For an occasional task, manual work or the source app's built-in option may suffice. Test Make when a repeated task needs its connections or processing.

4. Learn where to read credits in Make

This built-in practice shows where credits appear without connecting another app. Our recorded Repeater and Set variable runs used two credits for one generated item and four for three. They do not establish your integration's cost or an empty-poll rate.

1. Click Create scenario, name it Credit practice and leave it Inactive.
2. Add Flow Control, then Repeater. Set Initial value and Repeats to 1. Under Show advanced settings, leave Step at 1. Save.
3. Add Tools, then Set variable. Set Variable name to sample_number. For Variable value, select the green i token under Flow Control 1 - Repeater. Do not type the letter. Save the module and scenario.

Enlarge image

Full Make editor showing Repeater with Initial value 1, Repeats 1 and Step 1.

×

Open full-size image

Enlarge image

Full Make editor showing sample_number with its value mapped to the Repeater i token.

×

Open full-size image

4. Open Canvas options beside the scenario name, enable Show credit usage, then close the menu.
5. Click Run once. Our recorded run showed one operation and one credit on each module, two credits total. In the Tools bubble, Operation 1's output was sample_number: 1.
6. Close the inspector, change Repeats to 3 and save. Run once again. Our recorded result was one operation and one credit for Repeater, plus three operations and three credits for Tools, four credits total.
7. Inspect the Tools operations. Our outputs were sample_number values 1, 2 and 3. Record your results and leave the practice Inactive.

Enlarge image

Full Make editor after a three-item run, showing one credit for Repeater and three credits for Set variable.

×

With Repeats set to 3, Repeater uses one credit and Set variable uses three. This single manual run costs four credits.

Open full-size image

Enlarge image

Full Make editor with the Set variable inspector showing three operations and sample_number 3 in the third output.

×

Open full-size image

See Make's Repeater (opens in a new tab), scenario variables (opens in a new tab) and credit indicators (opens in a new tab) instructions. Record your current displayed usage if it differs.

If the output is the letter i, reopen Set variable and select the mapped token. If Tools runs only once in the second test, check that Repeats is 3 and the modules are connected.

5. Measure the real task before relying on it

Test a safe sample in your real candidate. Check the output and record each module's credits, including empty polling checks, several arriving items and safe repeat or retry tests. Keep test writes separate from real work; repeats can repeat actions in another app.

Update your budget after a busy day or a change to modules, schedules or input size. Manual tests consume allowance too.

If the budget fails, first consider fewer checks, less work per period, or a supported instant trigger. Retest a changed workflow rather than assuming the saving. If you genuinely need more active scenarios or more frequent scheduled runs, Core lists unlimited active scenarios and one-minute scheduling (opens in a new tab). Those paid capabilities were not tested here. Check its current price, allowance and billing period before paying.

Make says scenarios stop running when credits run out (opens in a new tab). A workflow that cannot tolerate a pause needs an appropriate plan and a recovery process.

If the allowance fits your estimated workload, start with Make Free (opens in a new tab) and measure a harmless manual sample before scheduling anything. Compare actual credit use with your budget before deciding whether to pay.