Before you hire an n8n automation agency or expert, get clear answers on five things: what exactly will be built and how you will know it works, where it will run and who pays for hosting, who owns the workflows and the logins, how failures will be reported, and what maintenance costs after launch. An expert who answers these in writing is worth talking to. CentriWeb builds most client automations in n8n, so we are one of the kind of providers you might be comparing, and the questions below apply to us as much as anyone.
What an n8n expert does, and what to hire one for
n8n is a workflow automation tool that connects your business software and runs steps between them, for example moving a new enquiry into your CRM, texting the customer and alerting your team. Its documentation describes it as a fair-code licensed workflow automation tool that combines AI features with business process automation (n8n documentation). If you are new to it, our guide on what n8n is comes first.
People hire an n8n expert, consultant, developer or agency for work like this:
- Building a set of workflows for a business that has outgrown manual admin.
- Connecting a CRM, accounting, booking and job software that do not talk to each other.
- Adding AI steps, such as drafting replies or answering questions from the business’s own information.
- Rescuing automations that someone built and left.
The titles overlap. A “developer” usually writes custom code, a “consultant” advises and scopes, and an “agency” does both with several people. What matters is who will do the work and who will be there in a year.
Scope the job before you compare quotes
Prices vary because scopes vary. Write a one-page brief first, then give the same brief to everyone you speak to.
- The problem. What costs you time or money now, and how often? “We type each enquiry into three systems and miss some” is better than “we want automation”.
- The systems involved. Name every tool, and who administers each.
- What a successful run looks like. One example in plain words, from trigger to result.
- Exceptions. What should happen when data is missing, a customer replies or a service is down?
- Volume. Roughly how many times a day or week it will run. This affects plan limits and cost.
Ask each candidate to write back what they understood and what they would leave out. Someone who proposes a smaller first piece and builds from there is usually easier to work with than someone who promises everything at once. Our guide to what to automate first can help you choose the first job.
Hosting: who runs it, and who pays
n8n can run in two ways, and the choice changes who is responsible. According to n8n’s documentation, on n8n Cloud n8n handles infrastructure, maintenance, updates and scaling, with more limited configuration control. Self-hosted means you run it on your own infrastructure, with full control, and the maintenance and updates are yours (n8n, choose how to use n8n, as at November 2026).
Ask where your automations will run and in whose account:
- Your n8n Cloud account. You pay n8n directly and you can see everything. n8n lists its Cloud plans, which are priced in euros and limited by monthly executions, on its pricing page, as at November 2026.
- A server in your name. You pay the host, and the provider manages the server for you. Ask who handles security updates and backups.
- The provider’s own server. Cheaper to start and harder to leave. See the ownership questions below before you agree to this.
There is also a licensing point. n8n’s code is published under the Sustainable Use License, which, as summarised on n8n’s GitHub licence page, allows use and modification for internal business purposes or non-commercial or personal use, and distribution only free of charge and for non-commercial purposes. If a provider hosts n8n for you and charges for it, ask how the licence applies to the arrangement, and ask them to put the answer in writing. This is general information and not legal advice.
Ownership of workflows and credentials
This is the question owners most often skip, and it matters most if the relationship ends. Get these answers before you sign.
- Who owns the workflows? The contract should say you own what is built for you. n8n lets workflows be exported and imported, and keeps version history (n8n, manage workflows), so a clean handover is possible, but only if you are given access.
- Whose logins are used? Connections to your CRM, email and accounting should use accounts or access keys in your name, with the least access the job needs. They should not run through the provider’s personal login.
- Who holds the credentials? Ask where they are stored and who can see them. n8n’s documentation says credentials are created in a personal space or in a project (n8n, credentials), and that sharing of workflows and credentials between users needs a paid edition on self-hosted installs (n8n, community edition features).
- Can you take it away? Ask what you would receive if you ended the arrangement tomorrow: exports, documentation, and the credentials or instructions to replace them.
Error alerts and what happens when it breaks
Every automation fails eventually. A password expires, a service changes or an unexpected value arrives. The difference between a small problem and a lost month of leads is whether anyone finds out.
n8n supports this directly: each workflow can use an error workflow that starts with an Error Trigger and can send an email or Slack alert when an execution fails (n8n, handle errors). Ask the provider:
- Who gets the alert, and how fast do they respond?
- What is checked after launch, and how often?
- Will you see a simple log of what ran, and what failed?
- What is the process when a customer message was missed because of a failure?
Our guide to why automations break lists the usual causes.
Maintenance terms and what it should cost
Ask for build and upkeep to be quoted separately, so you can compare both. A good maintenance agreement says what is covered (monitoring, fixes when a connected service changes, updates), what is extra (new workflows), the response time and how to end it. Be wary of a monthly retainer that does not say what you get for it, and equally of a build with no upkeep, because someone will need to look after it.
We do not quote prices here because they depend on scope and country. Use the brief you wrote to get like-for-like quotes.
How to check an n8n automation agency or expert
n8n runs an expert partner programme, which at the time of writing was a closed pilot with an application review, and a directory of experts at experts.n8n.io (n8n Expert Partner Program, as at November 2026). The programme page does not mention a certification, so treat any listing as a starting point and not a guarantee. Look at the directory itself before you contact anyone listed.
Whatever route you use, ask for:
- A recent project like yours, described in detail, and a contact you can ask about it.
- A written statement of who will do the work.
- A sample of their documentation.
- Clear answers to the ownership and alert questions above, in writing.
Be careful of anyone who promises specific results, will not tell you where your automations will run, or insists on running everything through their own login. A provider who tells you when you do not need n8n, or do not need custom work at all, is usually worth more than one who sells every time.
CentriWeb designs, builds and looks after automations for businesses, as part of its AI automation services, and we start with the part that costs you most. If a simpler tool will do the job, we say so. For a wider view of the options, read Zapier, Make and n8n compared.