error fix
Credentials Of Type Aren't Known
The custom node error about credentials of a type not being known usually means the credential class is not correctly registered, exported, or included in the node package.
Match your incident first
Start with the symptom you can prove
OAuth provider says redirect_uri_mismatch
First check: Copy the callback URL from the credential screen and compare scheme, host, path, and trailing slash.
Wrong fix to avoid: Do not guess the callback path from memory or old screenshots.
Verify: Provider redirects back to n8n and the credential test passes.
Credential works in editor but fails in production execution
First check: Check credential test, scopes, token refresh errors, and worker/main env consistency.
Wrong fix to avoid: Do not recreate the workflow before testing the credential independently.
Verify: A production execution using the credential succeeds on the same node.
Credentials type is not known
First check: Compare installed node packages and n8n version across main and worker containers.
Wrong fix to avoid: Do not import workflows into production until the credential type exists there.
Verify: The credential type appears in the UI and a test execution can load it.
- Use when
- node development, custom nodes
- First check
- Confirm the node references the credential type name you expect.
- Time to check
- 5-10 minutes
- Next step
- Run the recommended steps, then verify a production execution.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
The custom node error about credentials of a type not being known usually means the credential class is not correctly registered, exported, or included in the node package.
Version awareness
Last reviewed 2026-05-21
Key Facts
- Error family
- Custom node development and testing.
- Likely cause
- The credential type cannot be discovered by n8n.
- Common area to inspect
- Credential class naming, exports, package files, and node credential reference.
- Fix category
- Correct the node package metadata and rebuild or reinstall the node.
Production Diagnostic Matrix
Turn checks into a brief| Exact symptom or log | Likely cause | First check | Wrong fix to avoid | Verification |
|---|---|---|---|---|
| OAuth provider says redirect_uri_mismatch | Provider app redirect URI does not exactly match the callback URL n8n generated. | Copy the callback URL from the credential screen and compare scheme, host, path, and trailing slash. | Do not guess the callback path from memory or old screenshots. | Provider redirects back to n8n and the credential test passes. |
| Credential works in editor but fails in production execution | Token expired, scope missing, worker cannot decrypt credential, or different runtime env is used. | Check credential test, scopes, token refresh errors, and worker/main env consistency. | Do not recreate the workflow before testing the credential independently. | A production execution using the credential succeeds on the same node. |
| Credentials type is not known | Custom/community node package is missing on one runtime or after upgrade. | Compare installed node packages and n8n version across main and worker containers. | Do not import workflows into production until the credential type exists there. | The credential type appears in the UI and a test execution can load it. |
| OAuth callback reaches n8n but returns 404 or wrong host | Public URL, reverse proxy, or base URL settings are inconsistent with provider settings. | Check WEBHOOK_URL/public editor URL and proxy forwarded host/proto headers. | Do not add multiple provider redirect URIs before proving which URL n8n actually emits. | The callback uses the public HTTPS domain and lands on the credential completion screen. |
| Provider accepts callback but API calls return 403 | OAuth scopes are insufficient or the app was approved with old permissions. | Compare requested scopes with the API action the node is trying to perform. | Do not store broader scopes than needed without documenting the reason. | A minimal API action using the same credential succeeds with the required scope. |
Recommended Steps
- Confirm the node references the credential type name you expect.
- Check that the credential class is exported and included in the package files.
- Confirm package metadata points n8n to the node and credential files.
- Rebuild the package and reinstall it into the test n8n instance.
- Restart n8n and test the node again.
Verification
- The credential type appears in the node credential selector.
- n8n loads the custom node without the unknown credential type error.
- The node can execute a simple authenticated request.
Warnings
- A stale installed package can keep showing the old error after you fix source code.
- Do not debug this as an end-user credential password problem; it is usually a node package discovery problem.