Crypto

Node catalog Transformations

On this page

Provide cryptographic utilities

Usage and specifics

A hash is one-way. HMAC needs a shared secret and does not encrypt data. Choose the algorithm required by the destination system.

Technical type : crypto. Runtime : nodulz.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`operation`	`enum`	`"hash"`	`hash`, `hmac`
`algorithm`	`enum`	`"sha256"`	`sha256`, `sha512`, `md5`
`input`	`string`	`""`	-
`secret`	`string`	`""`	-

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "operation": "hash",
  "algorithm": "sha256",
  "input": "",
  "secret": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.