Guide
Pabbly tasks explained, using one workflow we actually ran
Pabbly charges for actions against external apps and not for triggers or its own internal steps. That is genuinely unusual and we confirmed it in a live run. The number that caught us out was a different one: when our workflow broke, Pabbly retried it by itself and charged full price.
No link on this page is an affiliate link, and AXORD earns nothing from anything recommended here. We may use affiliate links in future; when a link is an affiliate link it will be clearly disclosed on the page that carries it. How we are funded.
What counts as a task
DocumentedPabbly states that it does not count tasks for internal apps such as Filter, Router, Text Formatter, Number Formatter, Schedule, Iterator, Date/Time formatter, Email Parser, JSON Extractor or Array Functions. (Pabbly, accessed 2026-09-24)
We tested itPabbly charged nothing for the webhook trigger or either iterator. In our tested workflow three of the steps were free and only the external calls were billed.
So the rule holds in practice, not just in the documentation. If your workflow does a lot of shaping — filtering, routing, reformatting — that work is free here in a way it is not on platforms that bill per module.
What our workflow cost
The workflow: receive an order, fetch its line items, write one row per line item, pointed at an endpoint we built and control. Free plan, 2026-09-22.
We tested itIn our tested 10-line workflow a successful fan-out cost 11 paid tasks and a 1-line order cost 2 — one paid task per line item, plus one for the fetch.
| Step | Paid tasks | Why |
|---|---|---|
| Webhook trigger | 0 | Triggers are not billed. |
| Iterators (×2) | 0 | Internal steps are not billed. |
| Fetch line items | 1 | External call. |
| Write row (×10) | 10 | One per line item. This is the part that scales. |
| Total | 11 | For a ten-line order. |
The estimating rule for a workflow shaped like ours is external actions per item × items, plus the one-off external calls. Internal shaping steps do not enter the arithmetic.
The number that is not in the documentation
We tested itA completely failing 10-line run cost the same 11 paid tasks as a successful one and wrote nothing.
We tested itBecause automatic re-execution is on by default, that failure then cost a further 10 paid tasks without notifying anyone. One broken order consumed 21 of our 100 free monthly tasks in about ten minutes.
It is worth being fair about this: Pabbly was the only platform of the three that recovered on its own, and when a destination is briefly down that is exactly what you want. The cost appears when the failure is persistent, because a run that cannot succeed is retried at full price and nothing announces it. The three-way comparison is in do failed automation runs cost money?
What people get wrong about this
- Assuming free internal steps make the platform cheap. They make the shaping free. The per-item external writes are still the bill.
- Forgetting the retry. Budgeting for successful runs only is how one broken order takes a fifth of a free monthly allowance.
- Comparing tasks to credits or executions. The same workflow cost 11 tasks here, 13 credits on Make and 1 execution on n8n Cloud. Those units do not convert.
Limitations of these numbers
Limitations and failure cases
- One workflow on a free plan on 2026-09-22. Not an average across accounts, plans or time.
- Checked 2026-09-24: Pabbly's pricing page advertises the free plan as 100 tasks a month AND as limited to 2-step workflows. Our 2026-09-22 test ran a longer workflow on the free plan. We have not established whether that limit changed, is applied differently in practice, or did not apply to our account — so we are publishing the discrepancy rather than explaining it away. The 100-task allowance, which our 21-task figure is measured against, is confirmed.
- Pabbly documents that some internal steps — Lookup Table, Delay and Code — are not free. Our workflow did not use them, so we did not measure them.
- We did not test whether automatic re-execution can be turned off, or what it costs across repeated failures beyond the run we observed.
- AXORD is not in Pabbly's affiliate programme and earns nothing from this page.
- Vendors change billing behaviour. Treat this as dated evidence, not a permanent property of the product.
Where to go next
- Our full assessment of Pabbly — including the parts of the interface we could not find.
- Credits, executions and tasks — the same workflow measured on three platforms.
- The Automation Decision Sheet — what to decide before you build. No email required.