Skip to content

Cryptography

Cryptography handles operations on sensitive data inside a workflow, including encryption, decryption, signing, verification, and key generation. Choose the action and key type that match the data exchange with the next system.

  • Category: Processing
  • Purpose: Encryption, decryption, digital signing, verification, and key generation
  • Inputs: input_data - Data to process
  • Outputs:
  • output - Result
  • success - Whether the operation succeeded
  • error - Error message when it did not
  • Configuration:
  • Action: encrypt, decrypt, sign, verify, generate. Default encrypt
  • Cryptography Type: symmetric (one shared key) or asymmetric (public and private key pair). Default symmetric
  • Cipher / Algorithm: aes-256-gcm (recommended), aes-128-gcm, aes-256-cbc, chacha20-poly1305, fernet, base64, rsa-oaep, rsa-sha256, rsa-sha512. Note that base64 is an encoding, not encryption — it provides no confidentiality
  • Secret Key / Passphrase: Shown for symmetric operations
  • RSA Key Source: provide or auto-generate. Shown for asymmetric operations
  • Private Key (PEM): Required for decrypt and sign
  • Public Key (PEM): Required for encrypt and verify
  • Signature (Base64): Shown for the verify action
  • Key Size (Bits): 2048 or 4096. Shown when generating asymmetric keys
  • Key Length: 128-bit, 256-bit, 512-bit. Shown when generating symmetric keys
  • Key Format: base64, hex, or url-safe
  • Text Input: Text to process when no connection supplies it
  • PBKDF2 Salt / PBKDF2 Iterations: Key derivation parameters
  • Usage: Fields appear and disappear based on the selected action and cryptography type. This node reports failures through its success and error outputs rather than stopping the workflow, so a failed decryption still leaves the run marked as completed.