Enter how often a workflow runs and how many billable steps it has, and Model Ruler normalizes that one workload into Zapier tasks, Make credits/modules, and n8n executions, then picks the public-plan floor each provider reaches. Same inputs always produce the same output — it is a planning estimate from a source-dated register, not a quote.
Normalizes one recurring workflow into Zapier tasks, Make credits/modules, and n8n executions, then selects the public-plan floor each provider reaches.
Formula: zapier_tasks = workflow_runs * billable_steps; make_credits = workflow_runs * make_modules; n8n_executions = workflow_runs
Audit coverage: Automation platform billing
What does this calculator compute?
It normalizes one recurring workflow into Zapier tasks, Make credits/modules, and n8n executions, then reports the cheapest public-plan floor each platform reaches from a source-dated automation pricing register.
What should I check before committing to a workload shape?
Per-operation/per-module pricing and run frequency drive the cost more than any single LLM step. Check how many module actions each run consumes and the monthly run count — automation platforms often charge per action, so a multi-step run multiplies quickly.
Is this a quote or a benchmark?
Neither. It is a computed estimate. Real-world cost varies by rate-limit shape, caching, token-count precision, and provider-specific discounts not reflected in the public pricing table.
Zapier, Make, and n8n public pricing floors reviewed from official source pages. This estimate normalizes tasks, credits/modules, and executions; confirm current provider pricing before purchase or production commitments. View methodology.