Search for what an n8n consultant costs and the published numbers disagree by an order of magnitude for the same described work, even though every one of them is describing something it calls an n8n automation.
Here are the bands that hold up across sources. Freelance n8n specialists on Upwork bill around $40 to $100 per hour, and senior specialists $125 to $250. Vetted marketplaces like Toptal charge more for the screening. In the quotes I see, a scoped single workflow runs $400 to $3,000 from a freelancer or small shop and $5,000 to $10,000 from an agency, and retainers cluster between $500 and $3,500 a month. The spread inside those numbers is the actual subject of this post, because it is where most budgets go wrong.
What an n8n consultant costs in 2026
The hourly figures are the most stable data point, because marketplaces publish them. Upwork's n8n listings run $40 to $100 an hour depending on how much AI-agent and API integration experience the person brings, with Fiverr lower and Toptal higher. Salary platforms put an in-house automation engineer in the US around $120,000 a year, roughly $58 an hour. Paid discovery engagements, meaning a real process audit with a written scope at the end, usually land between $1,500 and $5,000 in the proposals I see.
Project pricing splits by who is doing the quoting. From what I see quoted, small shops and independents price a single workflow at $400 to $3,000 and a multi-workflow system with an AI step at $1,500 to $4,500. Agencies quoting the same shapes start around $5,000 and reach $15,000 to $50,000 once compliance requirements, conditional routing, production monitoring, and an availability commitment enter the scope.
Rates also move hard by region, which the aggregate numbers hide. In Brazil, where I work from, a simple automation is priced at R$400 to R$900 per project and an intermediate one at R$900 to R$2,500, while, from what I see in the local market, entry-level salaried automation roles pay R$3,000 to R$5,500 a month. Same tool, same nodes, an entirely different arithmetic for the buyer.
One pattern is consistent everywhere: the hybrid model won. A fixed fee for the first build, then a monthly retainer covering hosting, monitoring, updates, and the fixes that follow when a connected API changes behavior. Pure project pricing invites scope creep. Pure retainer invites paying for nothing. The hybrid split is now the default across most serious automation shops.
What an n8n consultant actually does
Strip the marketing and n8n is a visual workflow builder with hundreds of prebuilt integrations, running either on n8n's cloud or on your own server. An n8n consultant is someone who decides the shape of the flow, chooses where it runs, defines what happens when an integration fails, and documents it well enough that your team can maintain it afterward.
Dragging nodes onto a canvas is the easy part, and honestly the part you should not pay anyone for. What you pay for are the decisions that never appear on the canvas: where to host, how credentials are stored, how workflows get backed up, how a change gets tested without touching production, and what the system does when a vendor returns 500s for forty minutes straight.
Why the same workflow gets quoted at $800 and $8,000
Price tracks the cost of failure far more closely than it tracks build complexity. Two workflows can have the same node count and belong to different price categories entirely, because one of them fails into a missing spreadsheet row and the other fails into an uncharged subscription.
A five-node flow that posts a daily summary to Slack is genuinely a few hundred dollars of work. A five-node flow that syncs orders to inventory across two systems needs idempotency, retry logic, dead-letter handling, alerting, and someone who has already been burned by a partial write. The second one takes the same afternoon to draw and an entirely different kind of care to make trustworthy, and trustworthy is what the invoice is for.
This is also why quotes that come in without a discovery conversation should be treated carefully in both directions. Underpricing usually means the person has not counted the maintenance they are about to create. Overpricing usually means a $3,000 problem is being scoped like a $30,000 one. I broke down the hire-versus-build side of this decision in more depth in do you need an n8n consultant?
Should you hire anyone at all?
Often not. If the workflow is self-contained and a failure costs you a missing report, build it yourself. If it sits on the critical path for revenue, customers or compliance, the consultant's fee is small next to one bad weekend. I walk through that decision, including the one question that settles most cases, in do you need an n8n consultant?
One case belongs here because it changes the price: the tangle. Dozens of workflows calling each other and outages that span three flows and a spreadsheet. That work is consolidating and instrumenting rather than building, and it's priced like an audit, not like a workflow. The e-commerce reporting automation I built had that shape: the n8n part was quick, and the data decisions took longer than the build. It's the kind of work I take on as n8n automation consulting.
The cost line nobody puts in the quote
n8n Cloud is priced in euros regardless of where you are. Starter is €20 a month billed annually, €24 billed monthly, for 2,500 executions, per n8n's published pricing. Pro goes to €50 annually. Executions are counted per workflow run rather than per step, which is why n8n stays cheaper than per-task tools on complex flows and why a polling workflow can still eat an entire Starter allowance in under two weeks.
Self-hosting removes the license cost entirely. The Community Edition has no execution cap, so your spend becomes the server, somewhere between $5 and $50 a month on a modest VPS. Updates, backups, monitoring, and security become yours. The deciding question: does someone on your team run Docker and configure SSL without turning it into a two-week project?
If yes, self-hosted almost always wins the arithmetic. If no, the euro invoice is the price of not thinking about it.
Freelancer or agency
A freelancer is cheaper and correct for a single well-scoped workflow anywhere in the $400 to $3,000 band. An agency costs more and buys continuity: a contract, plus coverage when the specific person who built your flow takes a holiday or changes careers.
In-house only makes sense when automation is part of the product. If the business runs on n8n, that $120,000 salary gets cheap fast, because the alternative is paying a third party a retainer to own your core operations. The same logic applies across technical hiring generally, and it is worth reading alongside the WordPress developer cost breakdown, which walks the same tiers with different numbers.
Comparing quotes
Before asking anyone for a number, write half a page: what the workflow does, which systems it touches, what breaks if each of them goes down, and the deadline. (The hiring post has the longer version of this checklist.) That page is the only fair way to compare proposals. Anyone quoting without reading it is guessing, and a guess in the $400 range is cheap. A guess on a critical-path flow is not.
What's the most expensive thing your automation could break, and did your last quote price it in?
If your automation has reached the point where failure costs customers and nobody on the team wants the pager, that is the work I take: n8n automation consulting with paid diagnostic and a handoff that leaves your team able to maintain it. Tell me what's breaking.