For most small accounting practices, n8n Cloud is the better start: Starter is $20 a month billed annually (20 euros where n8n shows euro prices) for 2,500 executions, hosted data sits in Frankfurt, and nobody has to patch a server. Self-host only when a client or regulator requires your own infrastructure and someone competent will maintain it.
The cost surprise runs the other way from what people expect. An execution is one run of a whole workflow, so a flow that chases 80 clients for missing documents counts once. The cost that matters for client documents is the hours spent keeping a self-hosted server safe, not the subscription.
What each choice costs, from n8n's own pages
n8n's pricing page shows dollars or euros depending on where you view it from, and the amounts are not always a straight swap. Starter is $20 a month billed annually (20 euros) for 2,500 workflow executions, and Pro is $50 (50 euros) for 10,000. The page says annual billing saves 17 percent against paying monthly. The Business plan, at $800 a month billed annually (667 euros) for 40,000 executions, is listed as self-hosted only, with a waiting list for a hosted version. Every plan includes unlimited users and workflows. The figures below are the dollar list prices; check which currency your checkout uses.
| Cloud Starter | Cloud Pro | Self-hosted Community | |
|---|---|---|---|
| Software fee | $20 a month, billed annually | $50 a month, billed annually | None |
| Executions included | 2,500 | 10,000 | No execution fee |
| Concurrent executions | 5 | 20 or 50 | Set by your server |
| Longest single run | 5 minutes | 40 minutes | Your configuration |
| Saved execution history | 2,500 runs, 7 days | 25,000 runs, 30 days | Your storage |
| Where data is kept | Frankfurt, per n8n | Frankfurt, per n8n | Wherever you host |
| Who patches it | n8n | n8n | You |
Two limits in that table matter for documents. A 5-minute cap on a single run on Starter is tight if one workflow reads a 60-page PDF through an AI model, and the 7-day history means you cannot go back three weeks to see what happened to a client's upload. Pro's 40 minutes and 30 days are the more realistic fit for a practice. Self-hosting removes the execution fee but not the work, and n8n's own documentation says self-hosting requires technical knowledge: setting up servers and containers, managing resources and scaling, and securing the servers.
How executions are counted, with a tally for a 160-client practice
Zapier-style tools charge per step. n8n charges per run of the entire workflow, and a run that loops through a list is still one run. For client document work that difference is large, so count by trigger, not by step.
Illustrative: a twelve-person practice with 160 clients runs three workflows.
- Inbound documents. A mailbox trigger fires for each email with an attachment; the workflow names the file, files it in the client folder and logs it. In a normal month, 300 such emails means 300 executions. In the month before a filing deadline it might be 900.
- Weekly missing-documents chase. One scheduled run each Monday reads the tracker sheet and drafts a reminder for each client with gaps. Four or five executions a month, whether it covers 10 clients or 100.
- Daily digest. One run each weekday morning listing what arrived overnight and what is overdue: about 22 executions.
A normal month is roughly 330 executions, and the deadline month about 930. Both sit inside Starter's 2,500. A step-counted tool charging 3 or 4 actions per inbound email would need roughly 900 to 1,200 tasks for the inbound emails alone in the same normal month, and the gap widens at the deadline. If the practice later adds an invoice-reading flow at 600 a month, the deadline month moves to about 1,500 and still fits. Only when the total approaches 2,500 does Pro make sense. Check usage on n8n's Insights dashboard each week during busy periods. The pricing table lists overage on Starter and Pro as "Capped" without spelling out what happens at the limit, so confirm in your billing settings before a deadline month whether runs stop or cost extra.
What a failed run costs you
n8n's pricing page says you pay only when a workflow runs from start to finish, which is helpful, but a failure that drops a client's upload is worse than a charge. Set an error workflow (the workflow setting n8n labels "Error Workflow") that emails the person responsible whenever any flow fails. Test it by pasting a deliberately wrong credential into a copy and confirming the alert arrives.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThree client document flows worth building first
Flow 1: filing inbound documents under the right client
Trigger: new email in a shared "documents" mailbox. Steps: read the sender and subject, match them to a client code held in a Google Sheet or your practice system, rename the attachment to 2026-11-04_ClientCode_DocType.pdf and save it into that client's folder. Where the match fails, move the email to a "needs a human" label and post to the team channel. Never file a guess: a document in the wrong client's folder is a confidentiality breach, not an admin slip.
A realistic mistake: two clients share a surname and one email address, so the lookup returns the first row. Make the match require the client code in the subject or the sender's exact address, and treat multiple matches as a failure.
Flow 2: classifying what arrived with an AI step
Many practices let clients send anything. An AI node can name the document type: bank statement, payslip, invoice, loan letter, other. Ask for one of a fixed list so the answer can be used as a folder or tracker column.
Prompt: Classify this document using ONLY one of: bank_statement, payslip,
supplier_invoice, loan_letter, pension_statement, other.
Return the label only. If unsure return other.
Output (illustrative): supplier_invoiceWhat you would fix: with "other" allowed, ambiguous items fall out for a human instead of landing in a wrong folder. Review the first 50 results by eye and keep a tally of misses by type; scanned handwritten receipts are the usual weak spot. Note that the text of the document goes to whichever AI provider your node calls, a point that matters for hosting (see below).
Flow 3: the weekly missing-documents chase
Trigger: a schedule, Monday 8:00. The flow reads the tracker (client, required document, received yes or no), groups the gaps by client, and creates one email draft per client listing exactly what is missing. A person reads and sends the drafts. The same idea, with the tracker design, is covered in building an AI tax organiser that chases missing documents.
Illustrative sample draft: "Hi [first name], to finish your return we still need the pension statement and the December bank statement. Reply to this email with them attached and we will file them straight away. [your name]". Short, specific and signed by a person.
For a ready-made build of the reading step, see n8n invoice processing with AI, and put a human sign-off step in front of anything that is sent.
Where your clients' data goes in each setup
Hosting location and AI-model location are two separate questions, and practices often answer only the first.
- n8n Cloud: workflow data, credentials and saved executions sit on n8n's hosted servers in Frankfurt, according to n8n's pricing page. Your workflow text is stored in execution history for the plan's retention period.
- Self-hosted: data stays wherever the server runs. If it runs in a data centre your provider picks, check the region in the provider's console, because the default may not be the region you assume.
- AI nodes: a document sent to a model leaves your n8n instance for that model's provider, whichever way n8n is hosted. Review the provider's data terms, or leave client names and numbers out of what the model sees.
- Saved executions: n8n keeps the inputs and outputs of runs so you can debug them, which means client document text may sit in the history. The workflow setting "Save successful production executions" controls whether successful runs are kept; turn it off for flows that carry client papers, and leave "Save failed production executions" on so you can still debug failures.
If you have clients whose data may not leave a given region, put that in the engagement letter and tell them where processing happens. For the wider question of what may reach an AI model, see is it safe to use ChatGPT with client data, and for the written security plan, a template for an AI tools security plan.
What self-hosting really takes, priced in hours
The free licence is not the price. Self-hosting a practice's document flows means someone must do each of these.
- Set up a server, a database, HTTPS and a login in front of n8n, so the editor is not open to the internet.
- Apply n8n and operating-system updates, and test them before they break a workflow.
- Back up the database and the encryption key, and prove a restore works. n8n encrypts stored credentials with that key before saving them to the database, so keep the key with the backup or the restored connections will not work.
- Monitor it: disk space, memory, failed runs, certificate expiry.
- Be reachable when it stops on the evening before a deadline.
Illustrative sums, with every number an assumption to replace. Say 12 hours to set up properly and 3 hours a month to maintain, valued at $80 an hour for an IT contractor: $960 once, then $240 a month, plus a small server and backup storage. Against that, Cloud Pro at $50 a month is cheaper for years. Self-hosting only wins on cost when you already employ or contract someone who maintains servers anyway, or when volume would push you past Pro's 10,000 executions every month. Compare with the general figures in n8n self-hosted versus cloud costs.
Features you give up on the free self-hosted edition
Without a licence key, self-hosted n8n runs as the free Community edition. Features such as version control with Git and SSO belong to paid editions, so a practice that wants staff logging in through the office identity system or its workflows backed up in Git should price the Business plan. At $800 a month billed annually it is a different decision from Cloud Pro. n8n also lists a Startup plan at 50 percent off Business for companies with fewer than 20 employees that qualify, so a small practice should check whether it does.
Access, credentials and who can see client files
Every connection an n8n workflow uses (the mailbox, the file store, the practice system, the AI provider) is stored as a credential, and a workflow runs with that credential's full permissions. Create one dedicated service account for the workflows rather than reusing a partner's login, and give it access only to the folders the flow needs. If the account can read every client folder, a mistake in a workflow can expose every client folder.
Illustrative: a practice gives the documents flow a mailbox account called "documents" and a file-store account that can write into the client folders but cannot read or delete older files. When a trainee later edits the workflow and mistypes a path, the worst outcome is a misfiled new document, not a deleted archive. On Cloud, also decide who may log in to the editor, because unlimited users on every plan makes it easy to add colleagues who then see execution history. Keep the editor to the two or three people who maintain the flows.
A first-year cost table you can overwrite
This is an illustrative comparison for the 160-client practice above in a year with one deadline spike. Replace every figure with your own quote.
| Line | Cloud Starter | Cloud Pro | Self-hosted Community |
|---|---|---|---|
| Subscription for 12 months (annual billing) | $240 | $600 | $0 |
| Server and backup storage (assumed) | $0 | $0 | Your provider's quote |
| Set-up time (assumed 12 hours at $80) | Included in your own build time | Included in your own build time | $960 |
| Maintenance (assumed 3 hours a month at $80) | $0 | $0 | $2,880 |
| Risk if a run fails at a deadline | n8n operates the platform | n8n operates the platform | You are the support desk |
On those assumptions self-hosting costs about $3,840 plus the server in the first year, against $240 or $600 for Cloud. The numbers could change a lot if your maintainer is salaried and already idle on Tuesdays, but the shape stays: the subscription is the small part of the self-hosted bill. Whether you want your own infrastructure is a risk and control question, and the cost is the price of that control.
Moving between the two later
Treat the first choice as reversible. Workflows export as JSON files, and n8n's exports include credential names and IDs but not the secrets, so any move means re-entering every connection and testing each flow again. Keep a one-page register as you build: workflow name, trigger, what it reads, what it writes, which credential it uses and who owns it. With the register, a move to a self-hosted server, or back, takes days of testing and no redesign.
Moving from Cloud to self-hosted is the usual direction, triggered by a client contract or by volume. Do it between filing seasons, run both instances side by side for two weeks with the old one switched to read-only duties, and only then deactivate the Cloud triggers. Two active copies of an inbound mailbox trigger will file every document twice.
How to tell the flows are working
Measure four things monthly and keep the numbers in the register.
- Misfiled rate: pick 20 documents at random and open them in the client folders. Target zero wrong-client files; any one is an incident to investigate.
- Unmatched rate: how many emails went to the needs-a-human label. Over 15 percent suggests your client codes are not in the subject lines, which is a client-instruction problem, not a workflow problem.
- Chase response: of the clients reminded on Monday, how many sent the missing item by Friday. Compare against the months before the flow.
- Executions used: against the plan limit, so you move up a tier before a deadline and not during one.
If after two months the misfiled rate is zero and the unmatched rate is falling, the flows are earning their place. If staff are quietly fixing filing mistakes without telling anyone, the numbers will look better than the work, so ask them directly.
A rule for choosing
Use these tests in order and stop at the first that applies.
- Do any clients, contracts or professional rules require processing on infrastructure you control? If yes, self-host, with a named maintainer and a written backup plan.
- Does the practice have no one who can maintain a server? Use Cloud.
- Does a flow need runs longer than 40 minutes or more than 10,000 executions a month? Revisit self-hosting, and price it with hours included.
- Otherwise, start on Cloud Starter for one filing season, move to Pro if you hit the limit or need the longer history, and revisit after the season.
Starting on Cloud costs little to undo. Workflows export as JSON files, so moving a tested workflow to your own server later is a matter of re-entering credentials, not rebuilding. If you want to compare against a different tool first, read Zapier, Make and n8n compared.
The first two weeks on Cloud
Week one: build Flow 1 on a test mailbox, with ten sample emails from colleagues, and confirm every failure path sends an alert. Week two: switch to the live mailbox for one team, keep drafts as drafts, and read the execution history daily. Write down the three things a new colleague needs to know about the workflow: what it files, what it refuses to file and whom it alerts. Only after that add the AI classification step, and only for document types you are comfortable sending to a model.
Questions a practice asks before choosing
Is self-hosted n8n free for an accounting practice?
The Community edition runs without a licence key and costs nothing in software fees. You still pay for the server, backups, updates, security and the hours of whoever looks after it. Business and Enterprise features need a paid licence key, and n8n lists the Business plan as self-hosted only.
Where does n8n Cloud keep my data?
n8n's pricing page says hosted plans store data in the EU, on servers in Frankfurt. A self-hosted instance keeps data wherever you put it. Separately, any AI model your workflow calls processes text wherever that provider runs, so check both locations.
What counts as an execution?
One run of a whole workflow, however many steps it has or how much data it handles. A workflow that loops over 80 clients in one weekly run is one execution. That is the main reason n8n often costs less than step-counted tools for document work.
What happens at the execution limit?
n8n's pricing table lists overage on Starter and Pro as capped, and says Business and Enterprise keep running past quota with possible overage charges. It does not spell out the Cloud behaviour at the limit in plain words, so check your billing settings, watch usage weekly and move up a tier before a filing deadline.
Further reads
- AI Engagement Letters for Accountants: Faster Drafts, Clear Scope — Say in the letter how AI and hosting are used.
- AI Readiness Checklist for Accountants, Solicitors, Consultants — Check the practice is ready before automating.
- How Accountants Use AI to Spot Errors in Client Books — A second use of AI once documents flow.
- What Is n8n, and Should a Small Business Use It? — Start here if n8n itself is new to you.
- AI Powered Bookkeeping Platform: How a Practice Chooses One — A test-file method for picking an AI bookkeeping platform: three real client months each, scored on accuracy, review time and cost per client.
- Power Automate for Accountants: Flows for Documents and Approvals — Route client uploads and manager sign-off with two auditable flows, then check the connector and credit costs before buying.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: n8n's pricing page in its dollar and euro versions (plans, execution counting, data location, limits) and n8n's documentation on Docker hosting, the encryption key, workflow settings and workflow export, all read on 4 November 2026. Cost scenarios for hosting time are illustrations, not quotes.