Workflow pricing is determined by the unit a vendor meters. Zapier bills successful actions as tasks, Make bills module activity and AI complexity as credits, n8n Cloud bills complete workflow executions, Pipedream bills compute time as credits, and self-hosted n8n shifts the meter to infrastructure and labor. A tool that looks cheap at 1,000 simple runs can become expensive when every run loops across 100 records or calls several AI services.
Pricing models compared
| Platform | Main billing unit | Best for | Cost trap |
|---|---|---|---|
| Zapier | Successful billable actions/tasks | Fast setup and widest SaaS connector coverage | Each downstream action can count at volume |
| Make | Credits for module operations; AI may use multipliers | Visual, branching, data-heavy workflows | Iterators, polling, retries, and long scenarios multiply use |
| n8n Cloud | Complete workflow executions with plan limits and concurrency | Technical multi-step and AI workflows | Sub-workflows, errors, and executions still need modeling |
| n8n self-hosted | Infrastructure and operations rather than vendor execution allowance | Teams needing control and high volume | Security, scaling, backups, upgrades, and support are not free |
| Pipedream | Compute-time credits for workflows, plus connected/API costs | Developers combining code and managed integrations | Slow code, waits, and external model usage increase cost |
| Gumloop | Node and AI usage expressed in credits | AI-native document, research, and enrichment flows | Per-item AI nodes can consume thousands of credits |
| Power Automate | User, process, capacity, connectors, AI, and hosted resources | Microsoft-centered enterprises | License design can dominate runtime economics |
Zapier: easiest, but count every action
Zapier connects more than 9,000 apps and provides a guided trigger-and-action builder, filters, paths, Tables, Forms, Chatbots, AI steps, and agent features. It is the fastest way for a nontechnical team to connect a form, CRM, email platform, and project tool.
Professional and higher plans include task allowances. A trigger normally does not consume a task, while each successful billable action can. A workflow that receives one lead, creates a CRM contact, enriches it, makes a task, posts to Slack, and sends an email may consume five tasks per lead. At 2,000 leads, that is roughly 10,000 tasks before retries or other workflows.
Zapier has simplified treatment of AI steps and code under its task model, but MCP calls and newer products can have specific rules. Use the live pricing and usage documentation. The broad connector library can offset a higher unit price by eliminating custom development.
Choose Zapier when time-to-launch and niche app support matter more than the cheapest high-volume execution.
Make: best visual value for complex flows
Make scenarios display routers, filters, iterators, aggregators, transformations, data stores, webhooks, HTTP calls, and error paths on a canvas. This is more expressive than a simple linear automation and accessible to a capable business technologist.
Make plans allocate credits. A module that reads a record, writes data, or posts a message can consume credit according to current rules. Processing an array item-by-item multiplies operations. Polling an app can run even when little useful data changes, while a webhook triggers only when an event arrives.
Make AI Toolkit supports Make’s provider or customer model keys. Standard, advanced, and premium AI operations can apply different credit multipliers, with separate provider charges when using a personal key. The pricing calculator spans 10,000 credits into millions, and eligible plans can buy extra bundles or automatic top-ups.
Choose Make for multi-branch cloud workflows where a diagram and per-module visibility aid operations. Inspect run history and credit use with 100 representative records.
Our pick: Make for most cost-conscious SMB automation; n8n for long technical workflows
n8n: execution pricing favors long workflows
n8n counts a complete workflow run as an execution on its hosted plans, regardless of the number of internal steps under the standard model. Current Cloud tiers offer different monthly execution allowances, concurrency, history, collaboration, environments, SSO, and support. Official help material has referenced Pro tiers around 10,000 and 50,000 executions; check the live plan because prices and packages change.
This can be economical for a 30-node workflow that would consume many tasks or operations elsewhere. n8n supports code, custom nodes, HTTP, AI models, vector stores, agents, databases, queues, and technical branching. It is especially attractive to developers and automation engineers.
One business event can still create several executions if it invokes sub-workflows, retries, or scheduled checks. Model the actual execution graph. External model, OCR, search, database, and API charges remain separate.
The Community Edition can be self-hosted under n8n’s license, removing vendor execution quotas but not cost. Production hosting needs PostgreSQL, encryption keys, backups, TLS, upgrades, queue workers or Redis where appropriate, monitoring, secrets, access control, vulnerability response, and skilled on-call ownership. Review the license for the intended hosted or commercial use.
Choose n8n when long workflows, custom code, AI orchestration, or hosting control justify greater technical responsibility.
Gumloop: credit-based AI-native workflows
Gumloop provides a visual builder centered on AI tasks such as web research, document extraction, classification, enrichment, and content generation. Credits reflect node use and expensive AI operations. Official documentation illustrates how a workflow enriching 100 contacts can consume thousands of credits when a per-item node is multiplied across the list.
The platform makes credit transactions visible in dashboards and exports, which helps budgeting. Still, a document’s length, model choice, item count, and retries can change use sharply. Run the largest representative PDFs and contact lists, not only small examples.
Choose Gumloop when the workflow is AI-heavy and built by an operations or research team that wants specialized nodes. Make or n8n is often better when most work is deterministic application integration.
Power Automate: licensing matters more than tasks
Power Automate provides cloud flows, approvals, desktop flows, process mining, AI Builder, and connectors across Microsoft and third-party services. The economic unit can be a premium user, licensed process, hosted bot, Copilot capacity, AI Builder capacity, Dataverse, or another entitlement.
A company with existing Microsoft licenses and standard connectors may have a low incremental cost. An unattended desktop process with premium systems and document extraction has a different bill. Tenant administrators should use Microsoft’s current licensing guide and calculator rather than translating it into a simple per-task price.
Choose Power Automate when Microsoft identity, compliance, Dynamics, SharePoint, Teams, and Windows applications define the environment.
Calculate cost with a representative workflow
Take an invoice flow processing 5,000 documents monthly. Each run downloads a file, performs OCR/extraction, looks up a vendor, writes four line items, posts a record, stores the source, and notifies finance. Ten percent require a retry and 15% enter human review.
For Zapier, count billable actions per invoice and per line item. For Make, count modules, iterator bundles, AI multipliers, polling, and retries. For n8n, count main and sub-workflow executions plus model and extraction services. For Pipedream, measure compute credits and external calls. For self-hosting, add infrastructure and engineer hours.
Calculate median and 95th-percentile cost per successful invoice, not just the platform subscription. Add overage, data transfer, premium connectors, model tokens, vector storage, OCR pages, enrichment, and monitoring.
Keep the “flat” plan from becoming an outage
Flat or execution-based pricing encourages long workflows, but complexity still costs reliability. Use idempotency keys so retries do not duplicate invoices or emails. Add explicit error queues, backoff for rate limits, schema validation, and alerts. Separate development and production credentials.
Log business reconciliation: source count, destination count, money totals, and exception state. A green workflow run does not prove that the correct record was updated. Version prompts and mappings, and test malicious instructions embedded in emails or documents.
Verdict
Zapier is worth its per-task premium for rapid setup and broad connectors. Make provides the best balance of visual power and price for an SMB. n8n offers superior economics for long workflows and technical teams, especially when execution-based pricing or controlled hosting fits. Pipedream is best for code-first integration, Gumloop for AI-heavy operations, and Power Automate for Microsoft estates.
Build the real workflow in two finalists and run 100 representative records. Choose based on cost per verified business outcome at 10× expected volume, including maintenance and exceptions—not the largest task allowance printed on the pricing page.