A small AI automation can look cheap right up until the invoice arrives. One recent r/aiagents post described a Zapier account that started around $70 a month and reached $847 after the workflow grew to roughly 24,000 tasks. That is not a weird edge case. It is what happens when a workflow is priced per successful action and then you add AI steps, retries, branches, and more volume.

n8n pricing page visual showing the execution-based model

The useful question is not whether Zapier is good or n8n is cool. It is whether your workflow has crossed the point where per-action billing costs more than a migration plus a modest server. The calculation is simple enough to do tonight, and it can save you from moving a fragile production workflow just because one month was expensive.

The bill math

Start with the workflow, not the plan name. Count how many times the trigger fires in a month, then count the successful action steps that run for each event. A four-action Zap handling 30 leads a day burns about 3,600 ordinary tasks in a 30-day month. Zapier treats the trigger as free in this count. The four actions consume the tasks.

AI makes that estimate less reliable. Zapier's current documentation says AI by Zapier uses model tiers with 1x, 3x, and 5x task rates. The default Advanced tier is 3x. A single AI action that looks like one box on the canvas can therefore consume three tasks per run. A Premium step can consume five. Zapier also says MCP tool calls use two tasks, while Lead Router uses five tasks per successful routed lead.

Write the formula in a spreadsheet or a text file:

monthly tasks = runs × successful action steps × AI multiplier

Then add the less obvious paths. Include error-handler actions, replayed successful steps, sub-Zaps, and branches that run only for some records. Do not multiply every step by the maximum. Measure each path separately. If 80 percent of records take a three-step path and 20 percent take a seven-step path, the weighted average is 3.8 actions per run before AI rates are applied.

The community example is useful as a warning, not as a price quote for everyone. The author reported a move from $70 to $847 at 24,000 tasks. Zapier's own pricing page now describes a shared task pool across Zap workflows, AI steps, code, MCP, and SDK. That means a new AI experiment can consume the same allowance as the boring CRM sync you have trusted for months.

The first practical move is to export 30 days of usage. If you cannot see task counts by Zap, copy the run volume and successful actions from each workflow's history. Mark every AI step as Standard, Advanced, Premium, or bring-your-own-account where applicable. The result does not need to be perfect. It needs to tell you whether you are dealing with 2,000 tasks, 10,000 tasks, or 24,000 tasks.

The migration decision

n8n changes the unit you pay for. Its official pricing page lists Starter at 20 euros per month when billed annually with 2,500 workflow executions, and Pro at 50 euros with 10,000 executions. In plain terms, Starter includes 2,500 executions and Pro includes 10,000 executions. n8n counts one full workflow run as one execution, regardless of how many steps the workflow contains. Its self-hosted Community Edition is available without a paid license key.

That difference matters most when one event needs many actions. Suppose a support intake workflow runs 4,000 times a month and performs six actions for each ticket, including one AI classification step. Zapier sees thousands of successful actions, with the AI rate adding another multiplier if you use Advanced or Premium. n8n Cloud sees 4,000 workflow executions. Starter is too small for that workload, while Pro covers it on the published limit. Self-hosted n8n removes the software execution charge, but it replaces it with hosting and maintenance.

Use three tests before moving anything.

Keep it on Zapier when the workflow is below your plan limit, the connected apps are the main value, and nobody on the team wants to own a server. A $20 or $30 bill is often cheaper than one afternoon spent repairing a broken webhook. Zapier also has a huge integration catalog, so rebuilding an obscure connector can erase the savings.

Try n8n Cloud when the workflow has predictable volume but you do not want to manage Docker, backups, TLS, and upgrades. The 2,500-execution Starter tier and 10,000-execution Pro tier make the ceiling visible. Run the same workflow in a test project, compare the execution count, and keep the Zap live until the replacement survives real payloads.

Self-host n8n when the workflow runs frequently, the connectors are ordinary HTTP, email, database, or webhook operations, and someone can respond when the server fails. n8n's hosting documentation supports Docker Compose and says a self-hosted installation runs as the Community edition without a license key. Your cash cost becomes the server, storage, backups, monitoring, and the time needed to maintain them.

Do not compare a Zapier subscription with a bare VPS price and call the difference profit. Add a monthly maintenance allowance. If a small VPS costs $7 and you spend one hour a month on updates, backups, and incident checks, the server is not really a $7 replacement unless that hour is worth zero to you. The honest break-even equation is:

Zapier monthly bill - (hosting + backup storage + monitoring + maintenance time) = migration savings

If the savings are $40 a month, a migration that takes 12 hours has a one-year labor cost of $480 before the first bug. If the savings are $600 a month, the same project deserves a serious look. This is why task count alone should not trigger a rewrite.

What breaks after the move

The easy demo is a webhook, an HTTP request, and a Slack message. Production is where the missing work appears. Export credentials carefully. Recreate rate limits. Decide how failed executions are retried. Preserve idempotency so a retry does not create a second invoice or send the same customer email twice. Keep the old Zap disabled but recoverable until the n8n version has processed a representative sample.

Start with one narrow workflow. Put its inputs into a test queue, run both systems against the same records when the destination supports it, and compare outputs. Keep a log of missing fields and timing differences. A migration is successful when the new workflow produces the same business result, not when the green check mark appears in a dashboard.

Queue mode is a separate decision. n8n's documentation says it uses a main instance for triggers, Redis as the message broker, and workers for executions. A basic queue setup therefore adds one Redis broker between the main process and its workers. It also warns that queue mode is not compatible with filesystem binary data storage and recommends PostgreSQL rather than SQLite for this setup. That is a real scaling path, but it is not part of a first weekend migration. A single instance is easier to back up and debug.

The safest sequence is boring. Measure task burn for 30 days. Rebuild one high-volume workflow. Run it beside the old version. Set an alert on execution failures and monthly usage. Move the next workflow only after the first one has handled retries and unusual payloads. If your bill is still stable and the maintenance burden feels worse than the savings, stay put.

Zapier's task pricing is not automatically bad. It is easy to understand only while workflows stay small. Once AI steps and multi-action paths become normal, the important number is no longer the number of Zaps. It is the number of billable actions created by one real business event. Calculate that number before the invoice teaches you.

For provider-level budgets after you choose an automation platform, see the analysis of AI spend control at the gateway.

Sources