error fix
N8N Credential Error
An n8n credential error usually means the selected credential type, authentication method, scopes, test request, or external service settings do not match what the node needs.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
An n8n credential error usually means the selected credential type, authentication method, scopes, test request, or external service settings do not match what the node needs.
Key Facts
- Credential library
- n8n documents many built-in credential types for app nodes.
- HTTP Request option
- HTTP Request can use predefined credential types or generic credentials for custom APIs.
- Custom node issue
- For custom nodes, unknown credential type errors can come from credential class names and package metadata.
- Security note
- Credentials are sensitive and should not be hard-coded into public workflows.
Recommended Steps
- Confirm the node is using the intended credential type.
- Open the relevant credential documentation for the service or node.
- Check required scopes, region, domain, API key, OAuth redirect, or account permissions.
- Use the credential test option when available.
- For custom nodes, verify the credential class name matches the node credential reference.
Verification
- The credential test succeeds where supported.
- The node can perform a low-risk read operation.
- A failed workflow no longer reports authentication or unknown credential type errors.
Warnings
- Do not paste API keys directly into node fields that should use credentials.
- OAuth credentials can fail because of external app settings, not only because of n8n.
Common Mistakes
- Using generic HTTP credentials when a predefined credential type exists.
- Missing OAuth scopes required for the chosen operation.
- Testing with an account that lacks access to the target workspace, base, sheet, or project.
- For custom nodes, mismatching the credential name in the node and credential class.
Examples
Credential type correct: yes
External app permissions/scopes correct: yes
Credential test passes: yes
Low-risk read operation works: yes
Write operation tested safely: yesFAQ
Why does the same credential work in one node but not another?
The second node may need different scopes, resource permissions, account context, region, or operation-specific access.
Is every credential error fixed inside n8n?
No. Many credential problems require changing the external app, OAuth app, API key permissions, or account role.