Crypto Node

Crypto Node — Not Supported

The n8n Crypto node is not available on indie.money.

Why

The Crypto node's HMAC and Sign operations require your actual private keys and secrets to be handed directly to the execution engine so it can run cryptographic functions locally. This is fundamentally incompatible with indie.money's security architecture.

On indie.money, credentials are stored in a Secure Vault and never leave that vault. The execution engine only receives proxy tokens — it never sees real API keys, passwords, or secrets. When a node makes an API call, the proxy transparently injects the real credential at the network boundary. Your secrets are never exposed to workflow code or the runtime environment.

The Crypto node breaks this model because it doesn't make API calls — it performs local computation (HMAC hashing, digital signing) that requires the raw secret material. Supporting it would mean exposing private keys to the execution engine, defeating the purpose of the Secure Vault.

The Hash and Generate operations don't need credentials, but shipping a half-working node with a confusing credential UI creates more problems than it solves.

Alternatives

There is no direct replacement on indie.money. If your workflow needs cryptographic operations, consider these options:

• Hashing or HMAC as part of an API call: Many APIs accept raw data and handle hashing server-side. Check if your integration supports this.
• External webhook: Call an external service you control that performs the cryptographic operation and returns the result.

n8n documentation

For reference on the original n8n Crypto node operations: Crypto node documentation