When you need an n8n developer, we build and look after n8n workflows for your business. Forms, your CRM, email, spreadsheets, payments and AI steps are connected in workflows that retry, alert a person when they fail and come with notes. n8n runs on your own server or in your own n8n Cloud account.
Your n8n workflow ran fine last month. Is it still running today?
n8n is quick to build in. What happens afterwards is where most of the trouble starts. n8n's own guides and a security firm's count show what a workflow server needs once it is live.
103,476
n8n servers reachable from the internet were potentially open to one critical flaw when Censys counted them
What we doWe put the n8n editor behind a login, limit who can reach it and agree who applies security updates.
What an n8n set-up needs after the first workflow.
Five problems business owners bring to an n8n consultant, and what we do about each.
Problem 01 · Server or cloud
I do not know whether to run n8n on my own server or pay for n8n's cloud.
What we do
We ask where your data has to stay, how many runs you expect and who will look after a server. If nobody will, n8n Cloud is usually the better home, because n8n applies the updates there. If you host it yourself, we install it, secure it and set up the backup.
A written recommendation
The account or server in your name
A secure login and limited access
A backup you can restore from
A simpler tool named when it fits better
Problem 02 · Silent failures
A workflow stopped working days ago, and I only found out when a customer complained.
What we do
n8n can run a separate error workflow when another workflow fails. We build one for you, so a failed run sends the workflow name, the step and the error to a named person. Unreliable steps are set to retry, and bad data takes its own path and is not dropped.
An error workflow on every workflow
A message to a named person
Retries on unreliable steps
Longer waits for services that stay down
A path for bad or missing data
Problem 03 · Credentials
Every password and key is inside n8n, and I am not sure who can see them.
What we do
n8n encrypts credentials before it saves them, and a person a credential is shared with can use it without seeing its details. Instance owners and admins can see all of them. So we keep that group small, give each connection only the access it needs and write down who holds what.
Credentials kept in n8n's own store
No passwords typed into workflow steps
A short list of owners and admins
The encryption key backed up safely
Community nodes reviewed before use
Problem 04 · Updates
We host n8n ourselves and nobody has updated it since it was installed.
What we do
n8n releases new versions often, and some of them fix security flaws. We read the release notes for breaking changes, test the update on a copy with your workflows, then update the live server. A backup is taken first, so there is a way back.
Release notes read before each update
Tested on a copy first
A backup before every update
Security fixes applied first
A named person who owns updates
Problem 05 · AI steps and cost
I added an AI step to a workflow and the bill from the model provider keeps growing.
What we do
An AI step sends text to a model, and the provider charges for each use. We keep AI to the steps that need judgement and use ordinary steps for the rest. We test the AI step on real examples, cap what it can spend at the provider and limit how often an agent step may loop.
AI only where a rule will not do
Tested on real examples first
A spending limit at the provider
A limit on agent loops
Payments and customer messages wait for a person
Three n8n security reports. One lesson: look after it.
Three public reports from 2026 show what happens to workflow servers that are left alone. They are about n8n users in general. None of them is our client.
01
Security research · January 2026
A flaw let outsiders take control of n8n servers without logging in
What happened
The security firm Cyera reported a flaw in n8n, CVE-2026-21858, with the highest severity score of 10.0. It said an attacker with no account could gain full administrative control of an n8n instance, and estimated that 100,000 servers were affected. Cyera reported it to n8n on 9 November 2025, and a fixed version was published on 18 November.
What we do about it
The fix existed weeks before the flaw was made public. We agree who applies updates on your n8n, and security fixes go first.
A fake Google Ads add-on for n8n stole account logins
What happened
Endor Labs reported a malicious package that posed as a Google Ads community node for n8n. It showed what looked like a normal credential form, then sent the OAuth credentials to an attacker's server while the workflow ran. Endor Labs noted that community nodes run with the same level of access as n8n itself.
What we do about it
We use n8n's built-in nodes where they exist. Any community node is reviewed with you before it is installed, and community packages are switched off when none are needed.
The US cyber agency listed an n8n flaw as being used in attacks
What happened
On 11 March 2026 the US agency CISA added an n8n flaw, CVE-2025-68613, to its Known Exploited Vulnerabilities catalog, based on evidence of active exploitation. It urged all organisations to fix listed flaws as a priority. Fixed versions of n8n had been listed in a Censys advisory in December 2025.
What we do about it
Attacks came months after the fix. We set an update routine at handover, with a named owner, so your server is not one of those left behind.
Live products we built, not n8n workflows. Open them and judge the build for yourself. Our automation work is for private clients and is shared on a call, with the client's agreement.
Why choose Sun Software for n8n automation services?
Building a workflow in n8n takes hours. Keeping it running takes a routine.
n8n is one of the tools we work with, and we are not tied to it. If a simpler tool or your own code fits the job better, we say so before we quote. For a US telehealth company, an automation we built now enrols and books a paying customer without the owner stepping in. That client is private, so the details are shared on a call. We do not promise savings. We promise workflows that are tested, watched and written down.
The Sun Software team
01
We say when n8n is wrong
A hosted tool such as Zapier or Make, or your own code, is sometimes the better answer. We tell you first.
02
Failures reach a person
Every workflow has an error workflow, and we show you the alert arriving before launch.
03
Your server, your account
n8n runs in your name, and you can remove our access whenever you choose.
04
Written so a second person can run it
Clear node names, notes in each workflow and a handover guide your team can follow.
Great....very professional, delivered on time and exactly as I needed. Exceptional. I always find Sunsoft very easy to work with, always helpful and I'll continue using their services for the foreseeable future. No need to go anywhere else.
Client in United KingdomOctober 2026 · Fiverr review
“
Excellent experience from start to finish. Communication was great, responses were always prompt, and the work was completed quickly. They captured the exact look and feel I wanted on the first try and delivered excellent value for the money. I would gladly work with them again and highly recommend their services.
Client in GermanySeptember 2026 · Fiverr review
“
Choosing SunSoft was exactly the right decision. Their professionalism, extensive experience, and attention to detail have really impressed me so far. It was a complex project that exceeded my expectations! I look forward to continuing to work with SunSoft!
Client in CzechiaAugust 2026 · Fiverr review
Questions about n8n, answered plainly
What do n8n automation services include?
The set-up, the workflows and the upkeep. We set up n8n on your own server or in your own n8n Cloud account, build workflows that connect your forms, CRM, email, spreadsheets, payment tool and AI steps, add error handling and alerts to each one, and look after updates, backups and notes.
Should we host n8n ourselves or use n8n Cloud?
Use n8n Cloud if nobody on your side wants to look after a server. n8n applies the updates for you there. Host it yourself if your data has to stay on your own server, or you need more control. Then installing, securing, backing up and updating it becomes your job, or ours.
Can you host n8n for us?
No. n8n's licence FAQ lets a company like ours install and maintain n8n on your server, but not host it for you as well. So n8n runs on a server you rent or in your own n8n Cloud account. You own it either way, and you can remove our access whenever you choose.
When is n8n the wrong tool?
When two or three apps need a simple link and nobody technical will look after it, a hosted tool such as Zapier or Make is usually the easier answer. When a workflow is central to your product and needs automated tests, your own code may be better. We tell you which before we quote.
Who can see the passwords and keys inside n8n?
n8n encrypts credentials before saving them. A person a credential is shared with can use it in a workflow but cannot view its details. The owner and admins of the n8n instance can view and share every credential, so we keep that group small and write down who is in it.
What do AI steps in a workflow cost?
An AI step calls a model from a provider such as OpenAI or Anthropic, and that provider bills you for each use. The bill grows with the amount of text and the number of runs. We use AI only on the steps that need it, set a spending limit at the provider and limit how many times an AI agent step may loop.
Can you take over n8n workflows someone else built?
Yes. We start by reading them. You get a list of what each workflow does, which ones have no error handling, which credentials they use and which version of n8n you run. Then we fix the risky parts first and write the notes that were missing.
What decides the cost of n8n automation?
You get a written proposal once we have seen the process and the tools involved. The server or n8n Cloud plan, and any AI model you use, are paid by you to their providers. We list them before we start. Three things decide it. Workflows and branches: How many workflows there are, how many steps each has and how many exceptions each must handle. Where n8n runs: n8n Cloud needs little set-up. Your own server needs installing, securing, backing up and updating. Care after launch: Whether we hand over and step back, or keep watching the alerts and applying the updates each month.
What happens after I contact you?
We reply within one business day. Then the work runs in 6 steps: Choose the tool and the home, Set up n8n, Build the workflows, Add the alerts, Test with real cases, Hand over or look after. Each step ends with something you can review.
1Talk About Your n8n Workflows
2We reply within one business day
3Discovery call
4Step one: Choose the tool and the home
Have a workflow in mind, or one that keeps failing?
Tell us what you want n8n to do, or send us a workflow that keeps failing. We start by reading the process and telling you whether n8n is the right tool for it.