DEV Community: Farzam Saadat

Client Onboarding Automation: From Intake to a Reliable Handoff

Farzam Saadat — Thu, 08 Oct 2026 16:14:56 +0000

Client onboarding automation uses a defined set of rules to turn an accepted project into organized records, workspace access, welcome instructions, and assigned next steps. With n8n, you can connect those steps across business tools. The useful starting point is a clear handoff: who starts onboarding, what information is required, and who takes over when something is missing.

An agency can send a polished welcome email while still leaving its project manager searching for files. A bookkeeping firm can create a client folder while still lacking the documents needed to begin work. Automating a single message does not solve the whole handoff. The process needs a shared record of what has happened and what remains outstanding.

What should you automate first?

Start with repeatable administration after a project has been accepted. A useful first workflow records client details, checks whether the project already exists, creates its workspace, sends approved instructions, and notifies the person responsible for delivery.

Keep scope approval, unusual access requests, and changes to commercial terms with a person. Before building anything, write down the event that authorizes setup. That might be an internal form submitted after contract approval. A public inquiry should not automatically receive access to a client workspace.

Define the information the workflow needs

A practical intake record contains a project reference, client or company name, contact email, service package, internal owner, and agreed start date. Add a checklist of required materials if different services need different inputs. Collect only information that has a defined purpose in the process.

Use a stable project reference rather than a company name as the main lookup key. A reference such as WEB-1042 identifies the engagement without relying on spelling or email capitalization.

Choose clear statuses: Ready for Setup, Setup in Progress, Awaiting Materials, Ready for Kickoff, and Needs Attention. Define who can change each status.

Design the workflow around five checkpoints

1. Validate the intake

Check the required fields before creating anything. Normalize the contact email and project reference, and reject blank ownership fields.

2. Check for an existing project

Look up the project reference before creating the record or folder. If it already exists, send the existing record for review or stop with a clear explanation.

3. Create and record the workspace

Create the project folder and save its identifier in the project record. Confirm the recipient and permission level before sharing.

4. Send useful welcome instructions

A welcome email should tell the client what to provide, where to provide it, who owns the next step, and when the team expects a response. Avoid requesting passwords by email.

5. Hand off to the delivery owner

Send an internal notification with the project reference, folder link, client contact, and current status.

Plan for partial completion

Imagine the folder is created successfully but the email step fails. Starting the entire process again could create another folder or resend earlier messages. Record completed stages and design recovery around the failed step.

Test the handoff before using real client data

Try a valid new project, a repeated reference, a missing email, an invalid owner, a sharing failure, and a failed welcome message. Check both the outputs and the status after each run.

Measure readiness, not just email delivery

Track time from approved intake to completed setup, projects awaiting materials, repeat submissions, and cases needing manual repair.

For an example of the initial setup stages, explore my client onboarding workflow demonstration.

Common questions

Can onboarding be automated without replacing our existing tools?

Often, the process can be designed around the tools already in use. Confirm access permissions, supported integrations, and the ownership of each record before committing to a build.

Does client onboarding automation require AI?

No. Required-field checks, folder creation, routing, and approved welcome messages can use explicit rules.

What should remain manual?

Keep relationship-sensitive decisions, unusual permissions, and final readiness approval with the appropriate person.

Build a clear starting point

Choose one service, one intake route, and a defined handoff. If you want help designing that process, discuss your client onboarding process.

For more workflow automation for small businesses, visit the homepage.

n8n vs Zapier vs Make: The Real Cost Math for Small Businesses

Farzam Saadat — Tue, 06 Oct 2026 19:25:27 +0000

By Farzam Saadat · October 1, 2026

Which automation platform actually costs less once you run real workflows? We break down tasks, credits, executions, hidden fees, and self-hosting, with numbers you can plug your own business into.

Choosing between n8n, Zapier, and Make usually starts with a feature checklist and ends with a surprise invoice. The three platforms look similar on their pricing pages, but they count usage in completely different ways. That one difference can make the same automation cost $9 a month on one tool and $150 on another.

If you run a small business in the USA and you are comparing workflow automation tools , the question that matters is not “which has the most features?” It is “what will this cost me at the volume I actually run?” This guide does the math for three realistic scenarios, shows the hidden costs that blow up budgets, and gives you a clear way to decide.

The short answer

Make is usually the cheapest cloud option for small teams running multi-step workflows.
n8n wins when volume grows, because it bills per workflow run, not per step. It is also the only one of the three you can self-host.
Zapier is the easiest to start with and has the biggest app library, but it becomes the most expensive as soon as workflows get long or frequent.

Why Automation Pricing Is So Confusing

Each platform charges for a different thing. Until you understand the billing unit, you cannot compare prices honestly.

Platform	What you are billed for	What that means in practice
Zapier	Tasks — each successful action step in a Zap	A 5-step Zap that runs once uses roughly 4 to 5 tasks. Long workflows multiply your bill.
Make	Credits — each module action in a scenario (renamed from “operations” in August 2025)	Every module that runs costs a credit, so multi-step scenarios add up, but credits are cheap.
n8n	Executions — one full workflow run, however many steps it has	A 30-step workflow still counts as one execution. This is n8n’s biggest pricing advantage.

Put simply: Zapier charges per step, Make charges per module, and n8n charges per run. The longer and more complex your workflows, the more that distinction matters.

n8n vs Zapier vs Make Pricing in 2026

Here are the entry-level paid plans as published in late September 2026. Prices are for monthly equivalents on annual billing unless noted.

Zapier	Make	n8n Cloud
Free option	Free: 100 tasks/month, simple 2-step Zaps	Free: 1,000 credits/month, 2 active scenarios
Entry paid plan	Professional: $19.99/mo annual ($29.99 monthly), 750 tasks	Core: about $9/mo annual ($10.59 monthly), 10,000 credits
Mid plan	Team: $69/mo annual ($103.50 monthly), 2,000 tasks, up to 25 users	Pro: $18.82/mo monthly, 10,000 credits, priority execution
Collaboration tier	Team plan (shared Zaps, folders, connections)	Teams: $34.12/mo monthly
Scaling model	Move up the task slider; cost climbs steeply	Buy larger credit tiers; overage credits cost 25% more

Pricing changes often. Zapier and Make both use volume sliders, so always confirm your exact tier on each vendor’s live pricing page before you buy. n8n lists cloud prices in euros, so your US dollar cost will shift slightly with exchange rates.

How we counted usage

Zapier: one task per action step (the trigger is free).
Make: one credit per module, including the trigger.
n8n: one execution per run, regardless of steps.

The Real Math: Three Small Business Scenarios

To make this concrete, we modeled three workflow loads. Each “run” is one trigger firing (a new lead, an order, a form submission) that then passes through several steps.

Scenario 1: Micro	Scenario 2: Growing	Scenario 3: Busy
Workload	300 runs/month, 5 steps each (e.g., lead form to CRM, Slack alert, welcome email)	2,000 runs/month, 8 steps each (e.g., order processing across store, accounting, shipping, email)
Zapier usage	1,200 tasks	14,000 tasks
Make usage	1,500 credits	16,000 credits
n8n usage	300 executions	2,000 executions
Zapier cost (est./month)	About $49	About $150 to $200
Make cost (est./month)	About $9 to $11	About $18 to $30
n8n Cloud cost (est./month)	€20 (Starter)	€20 (Starter) to €50 (Pro)
Annual cost range	Zapier ~$590, Make ~$110, n8n ~€240	Zapier ~$1,800 to $2,400, Make ~$220 to $360, n8n €240 to €600

These are estimates built from each vendor’s published pricing ladders and independent 2026 pricing breakdowns. Treat them as directional and verify against the live calculators. The chart below shows Zapier at the low end of its range, so it errs in Zapier’s favor.

What the numbers tell us

At very low volume, Make is the cheapest and Zapier’s polish costs you roughly five times more for the same workload.
In the middle, Make and n8n are close. n8n Starter is fine until you cross 2,500 runs a month or need more than 5 concurrent runs. After that, Pro is the sensible baseline.
At scale, the gap explodes. Zapier’s per-step billing multiplies every extra step, while n8n’s per-run billing stays flat. Independent comparisons put n8n 5 to 20 times cheaper than Zapier once volume passes roughly 15,000 to 20,000 executions a month.

Hidden Costs That Quietly Wreck Your Automation Budget

The sticker price is only half the story. These are the costs that surprise small businesses most often.

1. Polling triggers eat your quota

Many workflows check an app for new data on a schedule instead of reacting instantly. A trigger that checks every 15 minutes runs about 2,880 times a month, which alone uses most of n8n’s Starter allowance. On Make, a trigger polling every 5 minutes burns roughly 8,640 credits, which is about 86% of a Core plan. Before you pay for a bigger plan, ask whether you really need a 5-minute check or whether hourly would do. Webhooks (instant triggers) avoid the problem entirely.

2. Retries and failed runs

A misconfigured trigger or a looping workflow can use up a month’s quota in an afternoon. On Make, failed runs and retries still consume credits. On n8n Cloud Starter and Pro, workflows pause when you hit your limit rather than charging overage, which protects your wallet but can silently stop your business processes.

3. Overage pricing

Make charges 25% more for extra credits than for the credits already in your plan, so right-size your tier instead of relying on overage. Zapier lets paid plans run past their limit for a while, but at a premium rate, and then pauses Zaps.

4. AI and code steps

AI steps and code now draw from the same task pool on Zapier. Make charges 2 credits per second of code execution time. n8n includes monthly AI credits with each cloud plan, with more on Pro. If you plan to build AI-powered workflows, model that usage separately.

5. The “pricing cliff”

n8n’s Business tier costs roughly 13 times Pro for 4 times the executions. Zapier’s jump from Professional to Team is also steep if you simply need a second user. Know where your cliff is before you build your whole operation on one plan.

Self-Hosting n8n: Is “Free” Really Free?

n8n’s Community Edition is free under its Sustainable Use License, with no execution limits. You only pay for the server. A basic VPS runs about $5 to $20 a month, which compared with n8n Cloud Pro’s €50 saves roughly $40 or more per month, and far more against Zapier at scale.

But “free” ignores your time. Self-hosting means you handle updates, backups, security, SSL, and uptime. Here is the break-even math:

Break-even formula

Monthly savings (about $45) divided by your hourly value = hours of maintenance you can afford. At $40 per hour, self-hosting stops paying off once you spend more than about one hour a month maintaining it.

Self-host n8n if you are comfortable with Docker, have steady high volume, or handle data you want to keep on your own infrastructure. Stay on cloud if you want zero maintenance, nobody on your team is technical, or your volume is low enough that €20 to €50 a month is trivial next to your time.

Beyond Price: Ease of Use, Integrations, and Power

Zapier	Make	n8n
Ease of use	Easiest. Linear, beginner friendly, fast setup.	Moderate. Visual canvas with branching; some learning curve.
Integrations	Largest library (8,000+ apps).	3,000+ apps plus HTTP module.
Complex logic	Paths, filters, formatters; gets expensive when long.	Routers, iterators, aggregators; strong for data handling.
AI workflows	AI steps and agents, billed from your task pool.	AI toolkit; bring your own key.
Self-hosting	No	No
Best for	Non-technical users who need a niche app connection fast.	Budget-conscious teams who want visual power without code.

Which One Should Your Small Business Choose?

If this sounds like you...	Choose
You run a few simple automations, under about 750 tasks a month, and want the least setup	Zapier (Free or Professional)
You want the lowest cloud bill and are happy to spend an afternoon learning a visual builder	Make (Core)
You run long, multi-step workflows or expect volume to grow	n8n Cloud (Starter, then Pro)
You have technical skills (or a freelancer) and want unlimited executions on a tight budget	n8n self-hosted
You depend on a niche app that only Zapier supports	Zapier, and keep the workflow short
You build AI agents or custom API-heavy workflows	n8n

A practical tip: many small businesses start on Zapier or Make, then migrate their heaviest workflows to n8n once the monthly bill becomes painful. You do not have to pick one platform for everything.

Frequently Asked Questions

Is n8n really cheaper than Zapier?

At low volume the gap is small, and Make is often cheapest. As your workflows get longer and more frequent, n8n becomes dramatically cheaper because it counts one execution per run instead of one task per step.

Is Make better than Zapier for small businesses?

On price, usually yes. Make gives you far more usage per dollar and unlimited active scenarios on paid plans. Zapier wins on simplicity and the size of its app library.

Can I use n8n for free?

Yes. n8n’s Community Edition is free to self-host with unlimited executions, but you pay for hosting and your own time to maintain it. n8n Cloud has no permanent free plan, only a trial.

What is the cheapest automation tool for a small business?

For low to moderate volume, Make’s Core plan is typically the cheapest managed option. For high volume, self-hosted n8n costs the least in cash.

Does n8n count every step as an execution?

No. One full workflow run is one execution, no matter how many nodes it contains. A sub-workflow call counts as its own execution.

Can I switch platforms later?

Yes, but workflows do not transfer automatically. You rebuild them, so start with the platform that fits your expected volume and complexity.

Final Verdict

There is no single winner, but the math points clearly in one direction: the cost of an automation platform depends far more on how it counts usage than on its headline price. Zapier is the fastest way to get started. Make is the best value for most small teams in the cloud. n8n gives you the lowest long-term cost and the most control, especially if your workflows are long or your volume is climbing.

Before you commit, list your three most important workflows, count their steps, estimate monthly runs, and plug those numbers into the models above. Ten minutes of math now can save you thousands over the next year.

Need help building your automations?

Farzam Saadat designs and builds n8n workflows for small businesses, from lead routing to AI-powered processes. If you need workflow automation for small businesses, get in touch at automation@syedfarzamsaadat.com or WhatsApp for a free workflow review.

Sources and methodology

Plan prices and limits were checked against independent 2026 pricing breakdowns published in September 2026 (Jet Admin, Coworker, Toolradar, Hackceleration, and others) and the vendors’ public pricing pages as reflected in those sources. Where sources disagreed (for example, euro versus dollar pricing for n8n, or Make’s annual versus monthly rates), the most recently checked figure was used and ranges were shown. Scenario costs are estimates, not quotes.

Expense Report Automation with n8n: Design the Review Process First

Farzam Saadat — Sat, 03 Oct 2026 14:21:47 +0000

Expense report automation moves employee submissions through consistent data collection, checks, record creation, and review notifications. A useful workflow makes missing information and exceptions visible. It does not, by itself, establish whether an expense is legitimate, tax-deductible, approved for reimbursement, or paid.

Before choosing nodes in n8n, decide what your expense process needs to prove. Who submitted the expense? What was purchased? Is the record complete? Who reviews an exception? Where is the decision recorded? These questions determine whether automation improves control or simply moves incomplete information faster.

Separate intake, review, approval, and payment

Treat these as four different stages. Intake captures the request. Review checks the information against the company’s rules. Approval records an authorized decision. Payment settles the approved obligation through the business’s payment process.

Conceptual flow: validation and exception checks are automated; approval and payment stay with people and the business’s payment process.

A confirmation email should say that the expense was received, not approved. Similarly, a status such as No Exception Flagged should not be interpreted as a payment instruction. This distinction matters when employees and reviewers rely on automated messages to understand what happens next.

A first project can automate intake and review routing while leaving approval and payment in the team’s existing process. State that boundary explicitly in the workflow specification and employee instructions.

Choose fields that support the review

Capture a submission ID, employee identifier, transaction date, merchant, amount, currency, business purpose, and supporting-document reference where required by company policy. Include the project or department if costs need to be allocated. Store a submission timestamp separately from the transaction date.

The amount should be numeric, but a number alone is not enough: 250 USD and 250 EUR are different records. If the workflow supports only one currency, make that visible on the form. If it supports several, define how comparison thresholds work before building a conversion step.

Keep original submitted values alongside corrected values when a reviewer makes a change. A useful record explains what changed, who changed it, and why. Avoid overwriting the original business purpose or amount without an identifiable review history.

Apply explicit validation rules

Separate incomplete or invalid submissions from policy exceptions. A missing employee identifier is a data problem. An amount above a company review threshold can be a valid submission that needs additional attention. Each deserves a different message and status.

Decide how refunds, credit notes, and corrections are handled. A workflow designed only for positive reimbursement requests should route negative values to a separate process rather than silently discarding them. Test dates, blank fields, decimal amounts, and unexpected currency values.

Write the rules in plain language before translating them into conditions. For example: if the amount exceeds the company’s chosen threshold, retain the submission and notify the designated reviewer. The threshold is a business choice, not a universal accounting standard.

Flag possible duplicates without assuming fraud

A duplicate check can compare employee, merchant, transaction date, amount, and currency. A repeat receipt identifier can provide another signal when it is reliably captured. Normalize text carefully so minor differences in capitalization do not hide a match.

These checks produce candidates for review. Two legitimate purchases can have the same amount and merchant on the same day. Conversely, the same expense may be entered with a different merchant spelling. Keep the reason for the match visible and allow a reviewer to resolve it.

Distinguish duplicate expenses from repeated processing of one submission. A stable submission ID can stop the same intake event from creating another record after a retry. At higher volumes, enforce uniqueness in the storage layer; a separate spreadsheet lookup followed by a write can race with another execution.

Create a reviewer queue that people can use

Store the request with a status, exception reason, assigned reviewer, and review timestamp. Suggested statuses include Received, Needs Information, Review Required, Approved, Rejected, and Paid. Use only the statuses your actual process supports, and define who can set them.

The reviewer notification should include the submission reference and a link to the authorized record. It should explain why review is needed without spreading receipt images or unnecessary personal details across multiple inboxes. Restrict access to the people who need it.

For a modest pilot, a spreadsheet can make records easy to inspect. n8n provides integrations for Google Sheets and Google Drive. Storage choices still need to account for permissions, concurrency, retention, and how review decisions are recorded.

A worked example: three submissions, three outcomes

Consider a fictional business that has chosen USD 500 as an additional-review threshold. This is an illustrative internal rule, not a recommended legal or tax limit.

Submission A is a complete USD 86 request with no matching prior entry. Record it as received and place it in the normal review queue. Submission B is a complete USD 620 request. Preserve it and flag the amount rule. Submission C is USD 86 with the same employee, merchant, date, and currency as A. Flag a possible duplicate and show the matching record.

None of those outcomes automatically establishes reimbursement approval. The reviewer still considers the business purpose and supporting information. If C is a legitimate second purchase, the reviewer records the explanation instead of deleting the match history.

Test failure recovery as well as the happy path

Test a valid submission, missing fields, a boundary amount, a possible duplicate, a repeated submission ID, and a failed notification. For the USD 500 example, test 499.99, 500.00, and 500.01 so the meaning of greater than versus greater than or equal to is deliberate.

Also test what happens when the record is saved but the email fails. Recovery should not insert the same expense again. n8n’s error workflow mechanism can support failure alerts [S2], but someone must own investigation and recovery. Define the response before rollout.

Do not mark an item paid because an email was sent or an approval checkbox changed. If payment tracking is later added, use an authorized payment result and a traceable reference as the basis for that status.

Measure the result without overstating savings

Track missing-information rates, time to first review, unresolved exceptions, and manual touches per submission. Compare equivalent periods and record the number of requests in each sample. A faster intake step can coexist with a slow approval queue, so measure the stages separately.

My expense intake and review demonstration illustrates an initial rules-based approach using sample data. This guide describes broader design choices and proposed controls; it does not imply that every feature discussed is included in that demonstration. My accounting and finance background informs the emphasis on records and review boundaries.

Common questions

Can n8n automatically approve expenses?

A workflow can be configured to apply business-defined decisions, but that should follow an approved policy and clear authorization. The intake-and-review approach here keeps reimbursement decisions with a person.

Do I need AI to read receipts?

No AI is needed when employees submit structured fields. Receipt extraction is an optional extension. If added, validate the extracted amount, currency, date, and merchant before relying on them; unclear results should go to review.

Is this a substitute for accounting software?

This design coordinates submissions and review. It does not replace a general ledger, reconcile accounts, or determine tax treatment. Any later accounting integration needs explicit mappings and approval rules.

Start with one expense category

Pilot a narrow category with agreed fields, reviewer ownership, and test cases. To map an appropriate first version, discuss your expense workflow and share how submissions currently reach your finance team.

How Much Does n8n Automation Cost for a Small Business?

Farzam Saadat — Sat, 03 Oct 2026 12:19:51 +0000

By Syed Farzam Saadat | Published October 2, 2026 | Updated October 2, 2026 | 11 min read

n8n automation pricing has two main parts: the platform and the build. The platform costs about €20 to €50 a month on n8n Cloud, or roughly $5 to $40 a month if you host it yourself. The build, meaning the workflows themselves, typically costs from under $1,500 for a simple workflow to $5,000 or more for a connected system.

Most pricing pages only show you the first part, which is why small business owners are often surprised by the total. This guide breaks down every cost layer with 2026 numbers, shows how n8n counts usage, and walks through three worked examples so you can estimate your own first-year cost before you talk to anyone.

Key takeaways

n8n bills per execution (one full workflow run), not per step and not per user.
n8n Cloud: Starter €20/month for 2,500 executions, Pro €50/month for 10,000, billed annually.
Self-hosting: the software is free, the server is roughly $5 to $40/month, and upkeep costs your time.
Build cost: roughly under $1,500 for simple workflows, $1,500 to $3,500 for typical multi-step ones, $5,000 to $15,000 for connected systems.
The most common budget trap is a polling trigger that burns executions all month.

What does n8n automation pricing include?

n8n is a workflow automation platform that connects your apps (a website form, a CRM, email, WhatsApp, accounting software) and moves data between them without manual work. When people search for n8n automation pricing, they are usually asking about four separate cost layers:

Cost layer	What it covers	Typical cost pattern
1. Platform	n8n Cloud subscription, or a server if you self-host	€0 to €50/month for most small businesses; $5 to $40/month for a server
2. Build	Designing, building, testing, and documenting the workflows	One-time; from under $1,500 to $15,000 depending on scope
3. Connected tools	CRM, email platform, WhatsApp, AI model usage, and other apps	Varies by tool; often already in your budget
4. Ongoing care	Monitoring, fixes, and changes when apps update	A few hours a month, or a small retainer

A simple way to remember it: first-year cost = platform + build + connected tools + ongoing care. Most comparisons stop at the platform line, which is usually the smallest number.

How much does n8n cost per month?

n8n Cloud is priced by monthly executions rather than by seat. Here are the published plans in 2026. n8n lists prices in euros, and annual billing is about 17% cheaper than paying month to month.

Plan	Annual billing	Monthly billing	Executions / month	Concurrent runs	Best for
Community (self-hosted)	Free software	Free software	No plan limit (server-bound)	Depends on server	Technical users
Cloud Starter	€20/month (€240/year)	About €24	2,500	5	Solo owners and first production workflows
Cloud Pro	€50/month (€600/year)	About €60	10,000	20	Growing small businesses
Business	About €667/month	Quote or annual	40,000	Higher	Teams that need SSO, Git, and environments
Enterprise	Custom	Custom	Custom	200+	Large organizations

In US dollars, third-party 2026 breakdowns put Starter at roughly $20 to $25 and Pro at roughly $50 to $65 a month, depending on the exchange rate and billing choice. For most small businesses, Starter or Pro is enough. Business costs about 13 times Pro for four times the executions, so it only makes sense if you need its governance features.

What counts as an execution in n8n?

An execution is one complete run of a workflow, no matter how many steps it contains. If a new lead triggers a 10-step workflow 1,000 times in a month, that is 1,000 executions. Task-based tools such as Zapier count each action step separately, which is why the same automation can cost very different amounts on different platforms.

How fast do n8n executions add up?

Your workflow design affects the bill as much as the plan does. A polling trigger checks an app for new data on a schedule, and every check can count as an execution. A webhook trigger runs only when something actually happens.

Check frequency	Runs per day	Executions per month
Every 5 minutes	288	8,640
Every 15 minutes	96	2,880
Every 30 minutes	48	1,440
Every hour	24	720
Webhook (event-based)	Only when an event occurs	Equals your real event volume

A single workflow that checks every 15 minutes uses 2,880 executions, which already exceeds the 2,500 included in Starter. Use webhooks or native app triggers wherever the app supports them, and poll less often where it does not.

Is n8n free for small businesses?

The self-hosted Community Edition has no license fee and no execution cap set by a plan, so the software is free. You pay for the server instead. Published 2026 guides put a basic VPS at about $4 to $7 a month, a production-hardened setup at around $12, and heavier workloads (for example, 20,000 executions a month with memory-hungry workflows) at $20 to $40 for a server with 4 GB of RAM and 2 vCPUs. n8n Cloud has no permanent free plan, only a trial.

The catch is your time. Estimates for a healthy self-hosted instance run about 2 to 4 hours a month for updates, backups, and monitoring, with more in a month when a migration goes wrong. Cloud Pro costs roughly $43 a month more than a $12 server, so if your time is worth $40 an hour, self-hosting stops saving money once upkeep passes about an hour a month. For many small businesses, Starter or Pro is cheaper once time is counted. Self-hosting makes sense when volume is high, data must stay on your own server, or someone technical already looks after your infrastructure.

n8n's Community Edition is source-available under a fair-code license. Running it for your own business automation is the standard use; read the license terms first if you plan to resell n8n as a hosted service.

How much does it cost to hire someone to build n8n automation?

For most small businesses, the build costs more than the platform. Price depends on how many apps are connected, how much branching and error handling the workflow needs, how it is tested, and whether it includes documentation and handover. Published 2026 rate guides and agency pages point to these ranges:

Project type	Typical scope	Typical price range	Typical timeline
Simple workflow	One trigger, two to four apps, little branching (for example, form to CRM plus email)	Under about $1,500	A few days
Multi-step business workflow	Lead routing, onboarding, or invoicing with branching and error handling	$1,500 to $3,500	About 6 to 10 days
Connected automation system	Several workflows, CRM or WhatsApp links, hosting setup, testing, documentation, handover	$5,000 to $15,000	Several weeks
AI-enabled workflow	Adds model calls, prompts, and safeguards to any of the above	Added on top, plus AI usage fees	Varies

On hourly pricing, established automation studios publish rates around $100 to $150 an hour, and surveys of experienced solo specialists report $95 to $235 an hour. Lower-cost freelancers and offshore teams charge far less. Region and experience move these numbers a lot, so treat them as a map of the market, not a quote.

The cheapest quote is not always the cheapest outcome. A workflow with no error handling, no documentation, and credentials stored in someone else's account becomes a black box the moment the builder moves on. Ask for a written scope, error alerts, documentation, and credentials that live in your own accounts.

What else adds to the cost of n8n automation?

Connected app fees. A CRM tier, an email platform, or WhatsApp Business messaging charges its own fees, separate from n8n.
AI model usage. If a workflow calls an AI model, that usage is billed by the model provider, not by n8n.
Hosting extras. Self-hosting adds backups, SSL, and monitoring on top of the server price.
Maintenance. Apps change their APIs and login rules, and workflows occasionally need repair.
Runaway runs. A loop caused by a misconfigured trigger can use up a month of Starter executions in an afternoon.

Three examples: what n8n automation costs in the first year

These examples are illustrative. They combine the platform prices above with the middle of each build range, in US dollars at roughly €1 = $1.10 to $1.15.

Business	What the automation does	n8n setup	Platform cost (year)	Build (one-time)	First-year total
Local service business	New website enquiry goes to the CRM, the customer gets an instant email, the team gets an alert (about 400 webhook runs a month)	Cloud Starter	About $270	$800 to $1,500	About $1,100 to $1,800
Online store	Orders sync to accounting and shipping, with stock alerts and customer notifications (about 3,000 runs a month)	Cloud Pro	About $670	$1,500 to $3,500	About $2,200 to $4,200
Growing operations team	Six or more workflows across CRM, WhatsApp, and reporting (about 15,000 runs a month)	Self-hosted on a VPS	$240 to $480 (server at $20 to $40/month)	$5,000 to $15,000	About $5,200 to $15,500

Totals exclude connected app fees and your own time. The third example is self-hosted because 15,000 monthly runs exceed Pro's 10,000 executions, and the next cloud tier costs far more.

How does n8n pricing compare with Zapier and Make?

The platforms bill different units: Zapier charges per task (each action step), Make charges per credit (each module action), and n8n charges per execution (each full run). For short, low-volume workflows the gap is small, and Make can be the cheapest of the three. For long or frequent workflows, n8n's per-run model usually costs less. One 2026 pricing analysis puts n8n at 5 to 20 times cheaper than Zapier once volume passes roughly 15,000 to 20,000 executions a month.

Platform	Billing unit	Entry paid plan (annual billing)
n8n	Execution (one full run)	Starter, €20/month, 2,500 executions
Zapier	Task (one action step)	Professional, $19.99/month, 750 tasks
Make	Credit (one module action)	Core, about $9/month, 10,000 credits

How can you keep n8n automation costs down?

Prefer webhooks to polling. Event-based triggers only run when there is something to process.
Stop unnecessary runs at the source. Use filters in the source app or webhook conditions so runs only start when needed, because every started run counts.
Add error workflows and alerts. You find out about a failure or a loop in minutes, not at the end of the month.
Start with one high-value workflow. Automate the task that wastes the most hours first, then expand.
Choose a plan on executions and concurrency, not on price alone. Starter allows 5 concurrent runs, Pro allows 20.
Self-host only with capacity. Make sure someone can handle updates, backups, and security.
Agree a fixed scope in writing with any builder, including documentation and handover.

Which n8n option fits your business?

Choosing between n8n Cloud, self-hosting, and hiring a builder

Your situation	Best-fit option
Under about 2,500 runs a month and no technical staff	n8n Cloud Starter
2,500 to 10,000 runs a month, or bursts that need more than 5 concurrent runs	n8n Cloud Pro
Above about 10,000 runs a month, with someone technical to maintain a server	Self-hosted n8n
You need SSO, Git version control, or separate environments	Business or Enterprise
You have no time to build or maintain workflows	Hire a builder on a fixed, documented scope

How do you get an accurate quote for n8n automation?

Before you ask anyone for a number, write down five things: the process you want automated, step by step; the apps involved; your expected monthly volume; what should happen when something fails; and who will maintain it afterward. With those, any builder can give you a realistic scope instead of a guess.

If you want to see what a finished workflow looks like, including the diagram and a written breakdown, browse my n8n workflow projects. When you are ready to scope your own, contact me with a short description of your process and we can work out what is realistic.

Frequently asked questions about n8n automation pricing

How much does n8n cost per month?

n8n Cloud starts at €20 a month for Starter (2,500 executions) or €50 a month for Pro (10,000 executions) on annual billing. Monthly billing is about €24 and €60. The Community Edition is free to self-host, but you pay for the server. Business costs about €667 a month.

Is n8n free for small businesses?

The self-hosted Community Edition has no license fee, so the software is free. You still pay for a server, roughly $5 to $40 a month, and for the time to maintain it. n8n Cloud has no permanent free plan, only a trial.

How much does it cost to hire someone to build n8n automation?

Simple workflows often cost under $1,500. Typical multi-step business workflows run about $1,500 to $3,500, and connected systems with several workflows, hosting setup, and documentation range from about $5,000 to $15,000. Prices vary by builder, region, and scope.

What counts as an execution in n8n?

An execution is one complete run of a workflow, regardless of how many steps or nodes it contains. A 20-step workflow that runs once is one execution. Zapier, by contrast, counts each action step as a task.

Is n8n cheaper than Zapier?

Usually, once workflows get long or frequent, because n8n bills per run instead of per step. At very low volume the difference is small, and Make can be cheaper than both. Multiply steps per workflow by monthly runs to compare your own numbers.

Should a small business use n8n Cloud or self-host?

Choose Cloud if nobody technical will maintain a server, because n8n handles hosting and updates. Self-hosting suits high volume, data-control needs, or teams with someone who can manage updates, backups, and security, which takes roughly 2 to 4 hours a month.

Does n8n charge per user?

No. n8n Cloud pricing is based on monthly executions, not seats. Higher plans add collaboration features such as shared projects and admin roles, but the main cost driver is how often your workflows run.

The bottom line on n8n automation pricing

n8n automation pricing is easier to predict than it first looks. The platform is the small, visible cost: €20 to €50 a month for most small businesses, or a cheap server if you self-host. The build is the bigger one-time cost and depends on scope. The biggest surprises come from workflow design, especially polling triggers and missing error handling. Count your expected runs, pick the plan that fits, and agree a written scope before any work starts.

If you want a clear scope and price range for your own workflow, get in touch here.

Sources and methodology

Plan prices were checked against n8n's official pricing page as reflected in 2026 third-party breakdowns from Jet Admin (September 2026), Hackceleration (June 2026), CloudZero, and Coworker. Hosting costs come from Hackceleration, Arahi, and Rapidevelopers guides. Build ranges come from 2026 published rate cards, including a BetonAI survey of 54 automation operators and Achiya Automation's published rates; these vary widely and are not quotes. Euro prices are converted at roughly €1 = $1.10 to $1.15. Examples are illustrative. Prices change, so confirm current numbers before you buy. Last updated October 2, 2026.

About the author.

Syed Farzam Saadat is an n8n workflow automation developer who builds automations for small businesses. Pricing in this guide was last verified on October 2, 2026.