n8n-nodes-salted-hash

This is an n8n community node. It lets you generate salted hashes inside your n8n workflows.

Salted Hash is a simple utility that securely combines workflow data with a secret (salt) to produce a cryptographic hash. This is commonly used for signed URLs, token generation, or integrity checks.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

The Salted Hash node supports the following operation:

• Generate Hash:
  Create a hash from a template string. The template can include:
  • n8n expressions such as {{$json.field}}
  • The placeholder {{SALT}}, which will be replaced with the stored secret

Hash settings include:

• Algorithm: SHA-256 or SHA-512
• Output encoding: hex or base64url

Credentials

This node uses a single credential:

• Salted Hash Secret
  • A secret value (salt/key) stored encrypted in n8n.
  • The secret is never exposed in workflow data or logs.
  • The placeholder {{SALT}} in your template string will be replaced with this secret at runtime.

No external account setup is required. You only need to provide the secret once in the credential editor.

Compatibility

• Minimum n8n version: 1.0.0
• Tested against: n8n 1.50+
• No known compatibility issues.

Usage

1. Add the Salted Hash node to your workflow.
2. Create a credential of type Salted Hash Secret and provide your secret.
3. Enter a template string, for example:

test/{{$json.invoice}}/{{$json.debtno}}/{{SALT}}

n8n will resolve the expressions, insert the secret at {{SALT}}, and hash the result.
4. The generated hash will be returned in the field you specify (default: hash).

This design keeps the secret secure while letting you decide exactly where it appears in the string being hashed.

Resources

• n8n community nodes documentation
• Node.js crypto documentation

Version history

• 0.1.1 — Fixed template field mapping to resolve incorrect placeholder handling.
• 0.1.0 — Initial release with SHA-256 / SHA-512 support, hex and base64url encoding, and template-based salt insertion.