This page is for UK businesses that want automation they can see inside, extend with code and, if they choose, run on their own server. I design, build and document n8n workflows, either on n8n’s own cloud service or on hosting you control, and I make sure the personal data those workflows handle stays somewhere your privacy notice can honestly describe.
n8n is a workflow automation tool built around a visual canvas. Each workflow starts from a trigger, such as a form submission, a schedule or an incoming request, and passes data through a chain of steps called nodes. What sets it apart from the tools most small businesses meet first is that you can drop into JavaScript or Python at any step, call almost any system with a plain HTTP request, and host the whole thing yourself.
Where n8n is the right choice
I suggest n8n when one or more of these is true for a business:
- Data residency matters. You want enquiry, customer or patient data to pass through a server in a UK data centre, under your own account, rather than through a third party’s platform.
- The logic is awkward. Branches, loops over hundreds of records, merging data from two sources or reshaping a messy export are all comfortable in n8n. In simpler tools they turn into long, fragile chains.
- Volume would be expensive elsewhere. n8n’s cloud plans count a whole workflow run once, however many steps it contains, and a self-hosted copy has no per-run charge at all. A twenty-step workflow that runs thousands of times a month usually costs much less here than on a platform that bills every step.
- The system you need has no ready-made connector. If a supplier, booking system or industry platform offers an API (a documented way for software to exchange data), n8n can usually talk to it directly, without waiting for someone to publish an integration.
- AI steps need to sit inside a real process. n8n has nodes for language models and for building an AI agent that can call your own tools, so classification, drafting or extraction can run as one step in a workflow that still has normal checks around it.
Where it is not
I would steer you elsewhere if nobody in your business will ever open the editor, and the job is a handful of simple links between popular apps. Zapier or Make will do that with less to look after, and my glossary entry on Zapier and Make explains how those two differ. n8n has fewer prebuilt integrations than Zapier, its interface assumes you are comfortable with data structures, and a self-hosted copy needs someone responsible for updates, backups and security.
Two other cases where I would not use it. If what you need is a CRM with built-in sequences, buying that CRM is usually better than recreating it in n8n. And if you are an agency hoping to run one n8n server and sell access to clients, read n8n’s Sustainable Use License first: it is source-available rather than open source, and it limits use to your own internal business purposes. I set up each client’s instance in that client’s name.
Cloud or self-hosted: the decision that sets everything else
This is the first thing I settle with you, because it decides who looks after the server, what you pay and where personal data ends up.
| Question | n8n Cloud | Self-hosted |
|---|---|---|
| Who maintains it | n8n handles servers, updates and uptime | You, or whoever you appoint, handle updates, backups and monitoring |
| Where data is processed | n8n’s hosting region, which I confirm against their current documentation before you sign up | Wherever you put the server, including a UK region of a major cloud provider |
| Running cost | A monthly plan sized by workflow runs | Hosting plus the time spent maintaining it |
| Who it suits | Businesses without anyone technical in-house | Businesses with an IT contact, strict data requirements or high volumes |
Under UK GDPR, the company hosting your workflows is a processor acting on your behalf, so you need a data processing agreement with it. My guide to data controllers and processors explains the split. If the server or the cloud service sits outside the UK, the international transfer rules apply as well. Transfers to the EU and EEA are covered by UK adequacy regulations. A server in the US needs a recognised safeguard, such as the UK International Data Transfer Agreement (IDTA), the UK Addendum to the EU standard contractual clauses, or a provider that has joined the UK extension to the Data Privacy Framework. Choosing a UK region for a self-hosted VPS (virtual private server) avoids that question entirely.
One detail many setups miss: n8n keeps the input and output of every run so you can inspect it later. That log contains names, emails and whatever else passed through. I set a retention period that matches your privacy notice, so execution data does not quietly pile up for years.
What I build on n8n
Lead capture and routing
Website forms, ad platform lead forms and booking tools send each enquiry to n8n through a webhook. The workflow cleans the data, removes duplicates, writes the contact to your CRM, alerts the right person and logs the source campaign. Where you advertise, the same workflow can send confirmed sales back to Google or Meta so bidding learns from real customers rather than form fills.
Data syncing between systems
Keeping a CRM, an accounting package, a spreadsheet and an email platform in step is where n8n earns its keep. I build syncs that check before they write, so a record updated in two places does not overwrite the newer version.
Scheduled reports and alerts
Weekly figures pulled from ad accounts, GA4 and the CRM into one sheet or email, plus alerts when something breaks: a form that has had no submissions for two days, a budget overspending, or a feed that failed overnight.
AI steps with a person approving
Sorting incoming emails by topic, extracting details from PDFs, or drafting a reply for someone to check before it is sent. I keep a human approval step wherever the output reaches a customer or changes a record that matters.
How a build runs
- Scoping call. We go through the process as it runs today, step by step, including the exceptions your team handles by hand. I tell you then if n8n is the wrong tool.
- Hosting and access. I set up n8n Cloud or a self-hosted instance in your name, with a production database, encrypted credential storage, HTTPS, backups and an update routine. On self-hosted setups I note which software version is running and how to roll back.
- Written design. A short document listing each workflow, its trigger, the systems it touches, the personal data it handles and what should happen when a step fails.
- Build and test. I build against test records first, then run real cases with you watching the results land. Every workflow gets an error route that tells a named person when it fails, with the reason.
- Handover. A recorded walkthrough and written notes, so someone on your side can read, pause and adjust each workflow without me.
If you already use n8n and something keeps failing, I start with a review of the existing workflows and logs rather than a rebuild.
Problems I see most often
- A self-hosted instance on a default setup, with no backups, out of date by many versions and reachable by anyone who finds the address.
- Credentials shared through one person’s personal account, so everything stops when that person leaves.
- Workflows that fail silently. Nobody notices for weeks because no error route was set up.
- Execution logs holding years of personal data that the privacy notice says is deleted after twelve months.
- One giant workflow doing six jobs, which nobody dares to edit. Splitting it into smaller sub-workflows makes each part testable.
What you receive
- A working n8n instance, cloud or self-hosted, set up in your name with access you control.
- The agreed workflows, tested with real data, each with error alerts.
- Exported copies of every workflow, so you are not dependent on one server or on me.
- A design document covering triggers, systems, personal data and retention, which also helps when you update your records of processing.
- A maintenance checklist for updates and backups if you self-host.
The tools I use day to day, n8n included, are listed on my tools I use page.
Pricing
I write each quote in GBP after a free scoping call, and we agree it in writing before work starts. Your running costs are separate and paid directly to n8n or your hosting provider, so you can see exactly what the automation costs each month. Any support after handover, and how long it lasts, is agreed in the same written quote.
Next step
Write down the process you want automated, the tools involved and roughly how often it happens, then book a free 30-minute call. I will tell you whether n8n suits it, whether cloud or self-hosted makes more sense for your data, and what I would build first.