For owners7 min read
How to give a developer access without sharing passwords
Use team invites and limited roles instead of shared passwords, service by service, and know exactly how to remove access and rotate keys when the work ends.
Readn8n workflow takeovers: fix and finish self-hosted or cloud n8n
n8n is a workflow automation tool that can be self-hosted, often with Docker, or used as n8n Cloud. Workflows are stored as JSON and built from nodes, including Code nodes for JavaScript or Python, HTTP Request nodes for any API, and AI Agent nodes for language model tasks. Credentials are stored encrypted with an instance key, and larger setups run in queue mode with Redis and separate workers.
Common n8n takeover situations
Self-hosted instances are frequently left on an old version with no backups, and the execution log may have grown until the database slows everything down. Workflows built quickly lack error workflows, so failed runs go unnoticed. Webhook URLs change when the domain or tunnel used during testing disappears. AI agent flows may work in a demo but lack memory limits, tool restrictions or checks on the model's output.
Preparing the handover
Export your workflows as JSON and note which ones run in production. For self-hosting, record where the server runs, how it is updated and who holds the encryption key. Invite the developer as an instance user rather than sharing the owner login, and plan to rotate credentials afterwards. If workflows call code stored in a repository, the secret leak scanner checks it for exposed keys.
Open takeovers
No open takeovers yet
No open takeovers here yet
Be the first to post a project in this area, or browse every open takeover.
Developers who list this as a rescue specialty
Be the first rescue specialist here
Developers and agencies who finish other people's projects can create a free profile and list this as a specialty.
Free tools that help
Related guides
Related problems
Frequently asked questions
Can I move my self-hosted n8n to another server?
Yes, but you need the database and the same encryption key, otherwise saved credentials cannot be decrypted. Back up both before any move, and keep the key somewhere only you control.
Should I switch from self-hosted n8n to n8n Cloud?
It depends on your need for data control, custom nodes and maintenance time. Cloud removes server upkeep, while self-hosting gives more control. Mention your preference so developers can scope either path.