How can I enable the built-in Node.js crypto library in n8n code nodes?

Below is an explanation based on the n8n documentation:

No Special Cloud Configuration for Crypto

n8n Cloud already exposes the Node.js built‑in module “crypto” (along with the “moment” package) for use in code nodes. That means you don’t need to install or separately enable “crypto” when running on n8n Cloud. However, you may still encounter issues if you try to import the module in a way that isn’t compatible with n8n’s Code node restrictions.

Why the Error Appears

The error

  Cannot find module 'crypto' or its corresponding type declarations.

often appears when using TypeScript or an IDE that checks for type declarations. Even though the runtime environment (n8n Cloud in this case) provides crypto, the development environment might not be set up with its types. Another possibility is that the method of importing isn’t aligned with n8n’s Code node execution restrictions.

Workarounds

1. Use CommonJS Syntax:
   If you’re currently importing with ES modules (e.g. import crypto from 'crypto'), try using require instead:

   JSCopied
   const crypto = require('crypto');

   This approach is commonly used in code nodes and may help bypass the type-checking issue.

2. Ignore Type Checking in Code Nodes:
   Since n8n Cloud guarantees that the crypto module is available at runtime, you can safely ignore the type errors in your local development or configure your IDE to bypass type checking for Node.js built‑in modules.

3. Self-Hosted Option:
   If you require a different approach (for instance enabling additional built‑in modules via environment variables), note that such customization isn’t available on n8n Cloud. Instead, you’d need to run a self‑hosted instance of n8n where you have full control over settings like NODE_FUNCTION_ALLOW_BUILTIN.

Conclusion

There’s no special configuration needed on n8n Cloud to “enable” crypto since it’s already whitelisted. Rather, if you encounter the error, it’s related to how the module is imported or to local type checking. Using CommonJS (require) typically resolves the issue. If further customization is needed, consider a self‑hosted setup where you can adjust environment variables such as NODE_FUNCTION_ALLOW_BUILTIN as documented.

Hope this helps clarify the situation!