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.
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.
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.
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.