How much to charge for an n8n workflow
How much to charge for an n8n workflow comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is what the workflow is worth to the client in its first year, using their own time and error numbers. Your quote sits between the two. The job is usually something like routing new leads into a CRM, syncing orders between a store and a spreadsheet, sending a daily report, or putting an AI step in the middle of a process someone does by hand today.
I am not giving you a market dollar figure, because a two-step notification and a workflow that touches five systems with an AI step in the middle are different jobs. One number would mean nothing. Your rate and their numbers will get you closer.
Claude Code writes the code steps, works out API calls and drafts the logic quickly, and you can even connect Claude Code to n8n with MCP. That speed is why billing by the hour undersells you. The slow part is everything around the canvas: finding out how the process really works, waiting for logins, and deciding what happens when a step fails at 2am.
Calculate your floor and ceiling
Run this before you put a number on anything. Every input is yours or the client's, so you can show the working in the proposal.
The n8n workflow calculation
| Number | How to get it | Who supplies it |
|---|---|---|
| Floor | Your estimated hours for each line in the quote, plus a buffer you choose for revisions, times your hourly rate | You |
| Time value per year | Hours per month spent on the manual process, times what an hour of that person costs, times 12 | Client |
| Error value per year | Mistakes per month the manual process causes, such as a missed lead or a wrong invoice, times what one mistake costs them, times 12 | Client, with your judgment on the estimate |
| Ceiling | Time value plus error value | Calculated |
If the floor is above the ceiling, the workflow does not pay for itself. Say so and offer a smaller version, or tell them to keep doing it by hand. If the ceiling is far above the floor, you have room to price on value. How far you move toward it is your call, based on how solid their numbers are.
Find out what is at stake before you quote
Do not quote from a screenshot of a workflow someone found online. Ask five questions on the first call: what starts the process today, which apps it touches, who does it and how long it takes, what goes wrong now, and what happens to the business if the workflow stops for a day. The last answer decides how much error handling you need, and error handling is where the hours go.
Three kinds of n8n clients and what to price against
| Client | What they need | Price against |
|---|---|---|
| Solo owner or small team | One or two workflows between apps they already use, such as form to CRM to email | Owner hours spent copying data and leads that go cold |
| Operations-heavy business | Several workflows on orders, invoices or reporting, with retries and alerts | Staff time, late reports and the cost of one wrong order |
| Business adding an AI step | A workflow that reads, sorts or drafts with an AI model in the middle, plus human review | The hours of reading and sorting it removes, and the cost of a bad AI output going out unchecked |
If nobody can describe the process the same way twice, sell a paid mapping session first and quote the build after. Paid discovery for AI projects covers how to sell that, and client discovery questions before you quote has more questions to ask.
The CCC n8n Workflow Quote
Six parts of an n8n workflow quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Process map | Writing down every step, decision and exception before anything is built | What happens today when the data is missing or wrong? |
| Connections | Getting access to each app, setting up credentials, and custom API calls where there is no ready-made node | Who can give us admin access to each app? |
| Logic and AI steps | Branches, data mapping, code steps and any AI step, with the prompt and a review point | Which outputs must a person check before they go out? |
| Error handling | Retries, alerts to a named person, and what the workflow does with bad input | Who should hear about it when something fails, and how fast? |
| Hosting and setup | Setting up the account the workflow runs on, in the client's name, and moving it from test to live | Do you want it hosted for you, or on a server your team runs? |
| Handover and support window | A short walkthrough, notes on how each workflow works, and fixes after launch | Who on your side will own this once it is live? |
Error handling is your anchor line. A workflow that runs perfectly on the demo and silently stops when an app returns an error is worse than no workflow, because people stop checking the manual way. Quote it as its own line and explain why.
Hosting changes the client's running cost, so cover it in the quote. On n8n's hosted plans, price is set by monthly workflow executions, and one execution is a full run of a workflow no matter how many steps it has. That means a workflow that runs every minute costs the client more than one that runs once a day, even if the second one is more complex. There is also a free Community Edition the client can self-host, which moves the cost to running and updating a server. Pick with the client before you build, and put the choice in writing.
Agree who owns the account and the credentials
Workflows act in the client's name inside their apps, so put ownership in the proposal. The n8n account or server and every connected credential stay in the client's name, and they pay any plan or server costs directly. You get access that ends on an agreed date. If you build on your own account and they leave, they lose the workflow and you hold the keys to their systems, which is bad for both of you.
Then write down what happens when something outside your control changes. Apps change their APIs, logins expire and plan limits get hit. Say that those fixes fall under the support window or a retainer, not under the original price. Finally, define done: which workflows are live, what triggers each one, who gets the failure alerts, and which test runs passed. Once that is signed, a new workflow or a new app is a change request.
Always quote the support window
Workflows meet real data after launch. A field the client forgot about, a form someone fills in differently, or an app that rate limits at busy times all show up in the first weeks. If you have not quoted for that, you fix them for free while the owner decides automation does not work for them.
Put a fixed support window in the first proposal, next to the build price. Say what it covers: fixing failures, adjusting rules and tuning any AI step. Say what it does not cover: new workflows, new apps and new features. For ongoing work after that, offer a retainer. How to price a maintenance retainer covers the structure.
How to present the n8n workflow quote
- Lead with the outcome in the owner's words. One line on what is at stake, such as every new lead landing in the CRM with a follow-up sent the same minute, then the price.
- Offer three options. A starter with one workflow and basic alerts, a standard with the main workflows, full error handling and hosting setup, and a full version that adds an AI step, more apps and a longer support window. Make the middle one the clear best value.
- Show your calculation. Put their own time and error numbers in the proposal, with the error line labeled as an estimate.
- Itemize it. Process map, connections, logic, error handling, hosting and handover, then the support window as its own line. That gives the client a line to trim instead of a reason to say no.
- Take a deposit and tie the rest to milestones, with a passed test run as one of them. How much deposit to charge and how to structure milestone payments cover the schedule.
And skip hourly on the invoice, even though hours set your floor. Claude Code makes the build fast, so billing by the hour turns that speed into a pay cut. Why I stopped charging hourly for AI builds covers why. If the workflow sends email sequences, see how much to charge for email automation.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for an n8n workflow?
Work out a floor from your estimated hours times your rate, and a ceiling from the client's first-year time savings plus the cost of the errors it prevents. Quote between the two, itemizing the process map, connections, logic, error handling, hosting and a support window.
Should I charge per workflow or per node?
Not per node. Node count says little about the work, because the effort sits in access, error handling and testing. Scope by workflow so the client can see what they are buying, then price using your calculation.
Who pays for n8n hosting?
The client, on an account or server in their own name. Hosted plans are priced by monthly workflow executions, and the self-hosted Community Edition moves the cost to running a server. Agree which one before you build.
Should I charge a monthly fee for n8n workflows?
Quote a fixed support window with the build, then offer a retainer for ongoing fixes, API changes and new workflows. Keep it separate from the build price so the client sees what they are paying for.
Can Claude Code build n8n workflows?
Claude Code can write the code steps, work out the API calls and draft the workflow logic, and it can connect to n8n through MCP. You still own the process map, the testing and the decisions about what happens when a step fails.
Last reviewed by Duncan Rogoff on November 9, 2026
