How to manage environment level secrets in n8n?

@mylearnings_abu hello

If you have an Enterprise cloud plan, you can connect separate vaults for each environment using the External Secrets functionality; for self-hosted you can use Credential Overwrites via environment variable or REST endpoint; but if you’re on the cloud community edition a practical solution is to Create separate credentials for dev and prod, Store the URLs/configs in a database or Google Sheets and start each workflow by fetching the correct configuration based on an environment variable ENV=dev or ENV=prod