Crypto

Description

The Crypto node computes the hash or HMAC of a text value using standard algorithms (MD5, SHA-1, SHA-256, SHA-384, SHA-512). It is useful for signing webhook payloads, verifying data integrity, generating deterministic identifiers, or comparing against signatures provided by external services.

It is equivalent to n8n’s Crypto node.

The Hash mode generates a digest of the value. The HMAC mode generates an authentication code using an additional secret key. The result is encoded in hexadecimal or Base64 and stored in a data field.

Configuration

Parameters

Parameter	Type	Required	Description
action	select	Yes	hash (default): simple digest. hmac: authentication code with a secret key
algorithm	select	Yes	Algorithm: md5, sha1, sha256 (default), sha384, sha512
value	textarea	Yes	Text or expression to process. Supports dynamic variables
secret	text	No	Secret key (required when action is hmac). Supports dynamic variables
encoding	select	No	Output encoding: hex (default) or base64
outputKey	text	No	Field name where the result is stored. Defaults to hash

Output

The node adds the result to data in the field named by outputKey (default hash):

{
  "text": "hello world",
  "hash": "0b7f849446d3383546d15a480966084442cd2193"
}

Usage Examples

SHA-256 hash of a text

{
  "label": "Email hash",
  "action": "hash",
  "algorithm": "sha256",
  "value": "{{data.email}}",
  "encoding": "hex",
  "outputKey": "email_hash"
}

Sign a webhook payload with HMAC-SHA256

{
  "label": "HMAC signature",
  "action": "hmac",
  "algorithm": "sha256",
  "value": "{{data.payload}}",
  "secret": "{{data.webhook_secret}}",
  "encoding": "base64",
  "outputKey": "signature"
}

Generates the signature that can then be compared against the header sent by the provider.

MD5 in Base64

{
  "label": "Checksum",
  "action": "hash",
  "algorithm": "md5",
  "value": "{{data.content}}",
  "encoding": "base64",
  "outputKey": "checksum"
}

Notes

• The hmac mode strictly requires a secret; if missing, the node returns an error
• If an unsupported algorithm or encoding is given, the node returns a descriptive error
• If the input data is an object, the result is added without losing existing fields; if not, it is wrapped in { value, [outputKey] }
• MD5 and SHA-1 are not recommended for sensitive cryptographic use; use them only for checksums or compatibility
• Does not require credentials