Help for owners
The person who built our n8n has left and nobody knows how it works
Short answer
Start by finding who the n8n instance owner is, where it runs and where its encryption key is kept. On the free edition only the owner and the creator of a workflow or credential can access it. Secure access and take a full backup before anyone edits a workflow.
Does this sound like your situation?
- The person who built the automations has left or stopped replying.
- I do not know where n8n runs or who pays for it.
- I cannot log in, or I log in and see nothing.
- There is no documentation.
- Things run every day and I am afraid to touch them.
Why does this happen?
The instance belongs to one account
n8n has an instance owner. n8n documents that the owner email can be changed by the owner, and that this updates the existing owner account. It does not transfer ownership to another user. If the email is set through environment variables on the server, the UI controls are read-only.
Confirmed by docs.n8n.io
On the free edition, work is private to its creator
Sharing workflows and credentials is a paid feature. On the Community edition only the instance owner and the user who created a workflow or credential can access it, so a leaver's work can be invisible to everyone else.
Confirmed by docs.n8n.io
The encryption key may be known to one person
n8n creates a key on first start and saves it in the .n8n folder. Credentials are encrypted with it. Without that key, a restored database cannot be decrypted, so each login has to be entered again.
Confirmed by docs.n8n.io
Exports do not capture everything
n8n states a CLI backup of workflows and credentials leaves out users and roles, execution history, variables and instance settings. A fresh import shows the owner setup screen, and whoever completes it becomes the owner.
Confirmed by docs.n8n.io
The leaver's own logins may be inside
Credentials in n8n are often the leaver's personal accounts or API keys at other services. When that person's accounts are closed, workflows fail, and some might have been using logins nobody else can recover.
What can I do about it today?
- Find where n8n runsThe address, the hosting provider and the billing account. Pay attention to whose name the account is in.
- Do not delete the leaver's user or accounts yetTheir logins may be what the workflows use. Remove access only after you know what depends on it.
- Look for the server login and the encryption keyCheck password managers, old emails and handover notes. Do not guess or reset passwords on the server.
- Ask for a full backupThe n8n data folder, and the database if it is separate. Keep it where the leaver cannot change it.
- List the connected systemsOpen each credential and note which service it connects to and whose account it belongs to.
- Change nothing in the workflows for nowA first read-only look is enough.
When should I bring someone in?
- You cannot log in to n8n or to the server.
- The leaver had access to customer or payment data.
- Automations that earn or save money are running with no one who understands them.
How do I handle it?
- Secure access firstEstablish who can reach the server and n8n, and remove the leaver's access once I know what depends on it.
- Back upA full copy, including the encryption key, before any edit.
- Read and documentEach workflow's trigger, steps, connected systems and what happens when it fails, in plain language.
- Move logins to company accountsCredentials that use personal accounts are replaced with ones your business owns.
- Add alerts and an ownerError notifications, a named responsible person and a short runbook.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I take n8n over without the old developer?
Usually yes, if you control the server and hosting account. The encryption key and the owner login are the hardest parts.
Do I need a new n8n?
Not normally. Rebuilding is a last resort, since the existing workflows are the best description of what the business relies on.
Is the encryption key really that important?
n8n says credentials cannot be decrypted without it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.