Shapes

Convert and format values

Encrypt or sign

HMAC signatures, JSON Web Tokens, AES-GCM encryption and TOTP codes.

Nodes › SecurityOpen in Neblex
Good for
Signing and protecting values
Role
Works on the records in a flow
Find it in
Nodes › Security

When to use it

  • A partner requires a signed request or an HMAC over the body.
  • A JSON Web Token must be created or checked.
  • A value must be encrypted before it is stored or sent.

Reach for something else when

Example

Sign each outgoing payload with HMAC-SHA256 and send the signature in a header the partner verifies.

  1. Map fields
  2. Encrypt or sign
  3. HTTP request

How it works

Settings
Action: HMAC sign or verify (SHA-256, SHA-512 or SHA-1), Create or Verify JSON Web Token (Algorithm HS, RS, PS, ES or EdDSA, never none; Claims; Audience and Issuer), Encrypt or Decrypt (AES-GCM), TOTP code; Field; Write to; Key connection: an HMAC, symmetric or signing key connection to match.
Output
The signature, token, verification result, ciphertext, plaintext or code. Decrypted text is passed on only after its tag verifies; a token is verified with its signature, expiry, audience and issuer.
More in the guide

Add it to a flow

  1. Open the flow from Build › Workflows.
  2. Open Nodes and find Encrypt or sign under Security, or search for it. Click it or drag it onto the canvas.
  3. Drag from the previous step's output handle to its input, then open its settings with ✎ Edit.
  4. Run the flow and click the step to see the records it received and produced.