Workflow Automation / Cost comparison / Published v0.1
Tasks, Credits, and Executions: How Automation Platforms Count Usage
The cheapest-looking plan can become the wrong plan when its billing unit does not match your workflow shape.
The central pricing question is not “how many automations do I have?” It is “what does this platform count when one automation runs?” Five visible steps do not automatically equal five paid units: records, bundles, branches, checks, and connector behavior determine how often each step actually executes.
Four different counting models
| Platform | Primary unit to model | Practical implication |
|---|---|---|
| Make | Credits consumed by module actions | More modules and repeated operations can increase usage per run. |
| n8n Cloud | Complete workflow executions | A longer workflow can still count as one execution, subject to plan and feature limits. |
| Albato | Transactions plus the selected platform plan | Model both access/features and transaction capacity. |
| Pabbly Connect | Chargeable external action tasks | Triggers and vendor-listed internal tools are described as free; executed external actions drive task use. |
These are high-level translations, not interchangeable definitions. Consult Make, n8n, Albato, and Pabbly Connect before purchasing.
Build a usage estimate from the workflow
Write the happy path as numbered steps. Mark every branch, loop, retry, and external write. Then estimate three cases:
- Normal: expected monthly runs and typical record count.
- Busy: a realistic peak month rather than an arbitrary multiple.
- Failure: retries, duplicated triggers, and manual replays after an outage.
For an email attachment workflow, one incoming email may contain three files. A per-action model can count each file operation and each destination write. A complete-execution model may count the workflow once, but execution duration, concurrency, storage, or feature limits can still matter.
Do not compare list prices alone
A defensible comparison includes required connectors, polling frequency, minimum schedule interval, team access, execution history, error handling, data retention, support, and overage behavior. A lower monthly price is not cheaper if it requires more maintenance or cannot expose the failure details you need.
Self-hosted does not mean free
n8n offers a self-hosted path, but the relevant comparison is hosted subscription versus infrastructure, updates, backups, security, monitoring, and operator time. Self-hosting can make sense when control or integration constraints justify ownership. It is not a reliable cost shortcut for a team that does not want to operate software.
The decision worksheet
Before choosing a plan, record:
- monthly and peak workflow runs;
- average records handled per run;
- external actions per record;
- branch and retry frequency;
- required schedule interval;
- required connectors and premium features;
- acceptable history and recovery window;
- monthly maintenance capacity.
Use the Workflow Billing Topology Worksheet to translate those inputs into platform-specific ranges. Choose headroom from observed volatility, peak demand, continuity requirements, and the available manual fallback instead of applying one universal percentage. Recalculate after the first 100 runs, because actual branches and retries are usually more informative than a diagram. Then put the resulting software-cost assumption into the CriteriaDesk automation calculator.