N8n — n8n where to find credentials?
This guide explains n8n where to find credentials and how to manage them for Cloud and Docker users. You can find credentials in n8n under the Credentials area of the web app; n8n Cloud shows a credentials manager in the left menu, and Docker setups store keys in persistent volumes or environment variables.
What is a credential in n8n
A credential in n8n is a stored authentication item. It can be an API key, OAuth token, username and password, or other secret. Credentials let nodes connect to external services without exposing secrets in each workflow.
n8n where to find credentials for Cloud and Docker
In n8n Cloud, open the web app and choose Credentials or Credentials manager from the menu. The list shows saved credentials by name and type. Click a credential to view its metadata and which workflows use it.
For Docker, credentials are typically saved in the n8n database in the container. If you use a persistent volume, check the volume files or the external database you configured. Some Docker setups use environment variables for simple keys.
How credentials work in n8n
Nodes reference credentials by name. The node uses the stored secret when a workflow runs. This keeps secrets out of workflow JSON. You can share credential names across workflows to reuse the same authentication details.
When you edit or revoke a credential, all workflows that reference it use the updated details immediately. This behavior helps centralize authentication management.
Best practices for managing credentials
- Use n8n Cloud credentials manager for a central, web-based view.
- For Docker, store the database on a persistent volume or external DB to keep credentials safe across restarts.
- Limit who can create or edit credentials in your team.
- Use descriptive names and note which workflows rely on each credential.
- Rotate API keys and tokens regularly to reduce risk.
Summary
Finding credentials in n8n is easy once you know where to look. n8n Cloud offers a credentials manager in the web UI. Docker users find credentials in the container database or persistent storage. Keep names clear and follow basic security steps like rotation and access limits.
