Verdict
Make is a good fit when a workflow has branches, loops over rows, or needs a defined response when one step fails. Its credit model is simple to estimate once you count modules, and its error-handling options are detailed. The cost is time: you will spend longer learning the builder than with a two-step tool, and someone has to own the scenario after launch.
- Fits: teams automating multi-step processes across several apps, such as form to CRM to spreadsheet to chat alert.
- Fits: workflows that need routing (different actions per lead type) without paying for each branch; routers cost no credits. [1]
- Skip: one trigger and one action at low volume; the free tiers of simpler tools may cover it.
- Skip: no one available to check failures weekly; scenarios deactivate after repeated errors. [4]
How credits are counted
Credits are Make's billing unit. Most actions consume 1 credit; reading, searching, creating, updating, deleting and transforming data all count. Router modules and the error handler modules do not. [1] Make's help adds that 1 operation equals 1 credit regardless of input or file size, while some AI features use credits based on tokens, file size, page count or processing time. [2]
| Plan fact | Value | Source |
|---|---|---|
| Free plan credits | 1,000 per month | [1] |
| Free plan schedule | Minimum 15 minutes between runs; the lowest regular interval Make documents is one minute | [3] |
| Extra credits | Bundles of 1,000 or 10,000; Core, Pro and Teams can auto-purchase 10,000 | [1] |
| Annual billing | Pro and Teams get a yearly pool; Core always gets monthly credits | [7] |
| Per 10,000 monthly credits | 5 GB data transfer, 10 MB data storage, 10 MB incomplete executions, 667 queued webhook items | [1] |
| Paid plan prices | Not displayed to us on October 29, 2026; check at checkout | [1] |
Worked credit math against Zapier and Pabbly
Example: a webhook receives a new lead, then three actions run: add a spreadsheet row, add the subscriber to an email list, and post a chat alert. Assume 300 leads a month. We count the Make trigger as one module operation; confirm against your own scenario history, because trigger counting is the most common source of surprise.
Zapier does not count triggers or polling, and Filter by Zapier uses no tasks; its Professional plan starts at 750 tasks for $19.99 a month billed annually or $29.99 monthly, and the free plan allows two-step Zaps only. [8] Pabbly Connect counts only actions on external apps; triggers and internal steps such as filters, routers and formatters are free. [9]
- Add a router with two branches (for example, high-value leads also go to the CRM): Make adds no credits for the router itself, only for the extra module that runs. [1]
- Add a polling trigger instead of a webhook and your schedule matters; see our polling credit budget guide and measure a day of history before committing.
- Doubling volume to 600 leads gives 2,400 Make credits, 1,800 Zapier tasks and 1,800 Pabbly tasks; price each at the tier that covers it on the day you buy.
| Tool | Billed units per lead | Units per month (300 leads) | Fits which tier |
|---|---|---|---|
| Make | 4 credits (trigger plus 3 actions) | 1,200 credits | Over the 1,000 free credits; needs a paid plan or fewer modules [1] |
| Zapier | 3 tasks (trigger free) | 900 tasks | Over the 750-task Professional starting tier and not possible on Free (multi-step) [8] |
| Pabbly Connect | 3 tasks (trigger free) | 900 tasks | Over the 100-task free plan; within the 10,000-task Standard plan [9] |
The scenario builder: strengths and learning curve
Make's canvas shows every module, route and handler, which makes complex flows easier to audit than a long linear list. Instant webhook scenarios run in parallel by default, and you can switch on sequential processing when order matters, such as updating the same record twice. [6] Webhooks accept up to 300 requests per 10 seconds before returning HTTP 429. [6]
The learning curve comes from the same depth: bundles, iterators, mapping and handler choices are concepts a two-step tool hides. Budget a few hours to build and break a test scenario before moving a live process.
Error handling: strong, but you must configure it
With no handler and incomplete executions turned off, Make applies Rollback: the run stops with an Error status. A scheduled scenario is deactivated after 3 consecutive errors by default, and an instant (webhook) scenario is disabled immediately after an error. An operations-limit error (OperationsLimitExceededError) disables scheduling immediately. [4]
- Turn on incomplete executions for any scenario that writes to a system of record; it is off by default. [5]
- Incomplete-execution storage is limited by your usage allowance (10 MB per 10,000 monthly credits), so clear resolved items. [1] [5]
- Skip and Resume mark failed work as Success; use them only where losing that item is acceptable.
| Handler | What it does | Run status |
|---|---|---|
| Skip | Drops the failing bundle and continues | Success [4] |
| Retry | Stores the bundle as an incomplete execution for automatic or manual retry | Warning [4] [5] |
| Resume | Substitutes a value you define and continues | Success [4] |
| Commit | Stops and keeps changes made so far | Warning [4] |
| Rollback | Stops and reverts transactional changes (the default) | Error [4] |
Before you pay: a short evaluation plan
Use the free plan to answer the questions that decide cost and reliability.
- Build your real workflow and run it on 20 test records; read credits per run in the history.
- Multiply by monthly volume, add 20% headroom, and compare with Zapier and Pabbly unit counts for the same workflow.
- Break one step on purpose and confirm your handler and notifications behave as intended. [4]
- Decide who checks the scenario weekly and who is alerted on deactivation.
- Check the paid price for your credit tier at checkout and whether you need monthly or annual credits. [7]
Watch demos / Official walkthroughs
See how the tools work.
Videos load from YouTube only when you press play. These are provider videos, not our own product tests.
Make / Official video
Make—Building Your First Automated Workflow from Scratch
What to look for: Follow how modules connect and how data moves through the first workflow.
Watch on YouTubeQuestions before you decide
What is a Make credit?
Make's billing unit. By default 1 operation equals 1 credit, regardless of data size; some AI features use more, based on tokens. Router and error handler modules do not consume credits.
What happens when I run out of credits?
Make's error-handling page says an operations-limit error (OperationsLimitExceededError) disables scheduling immediately. Make's credits page lists the ways out: upgrade, buy extra credits in bundles of 1,000 or 10,000, or turn on auto-purchase (Core, Pro and Teams). Separately, each webhook queue holds 667 items per 10,000 monthly credits, up to 10,000, and rejects data beyond that.
Does an annual plan give me all credits up front?
On Pro and Teams, yes: annual subscribers draw from a yearly pool. Core users always receive monthly credits, even on an annual subscription.
Do polling triggers cost credits when nothing is new?
Make's help pages we checked do not state this. Run the scenario for a day and read the credit usage in its history before choosing a schedule.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make pricing and usage allowance Accessed 29 Oct 2026
- Make Help: Credits Accessed 29 Oct 2026
- Make Academy: Scheduling your scenario Accessed 29 Oct 2026
- Make Help: Overview of error handling Accessed 29 Oct 2026
- Make Help: Incomplete executions Accessed 29 Oct 2026
- Make Help: Webhooks Accessed 29 Oct 2026
- Make Help: Monthly and annual subscriptions Accessed 29 Oct 2026
- Zapier pricing Accessed 29 Oct 2026
- Pabbly Connect pricing Accessed 29 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.