Actions40
- Job Actions
- Account Hierarchy Actions
- Cryptography Actions
- Customer Hierarchy Actions
- File Explorer Actions
- Generic API Actions
- Invoice Actions
- Mediation Actions
- Order Actions
- Quote Actions
- Subscription Actions
Overview
The Cryptography → Encrypt Message operation in this n8n node allows you to encrypt a plain text message using AES encryption with a user-provided passphrase. This is useful for securely storing or transmitting sensitive information within your workflows, such as passwords, API keys, or confidential messages.
Common scenarios:
- Encrypting sensitive data before saving it to a database or sending it over an insecure channel.
- Preparing secrets for later decryption by another workflow step or external system.
- Ensuring compliance with security policies that require data at rest or in transit to be encrypted.
Practical example:
You can use this node to encrypt a user's password before storing it in a custom CRM, or to protect API credentials when passing them between different automation steps.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects the authentication method for Opencell API (not directly used in encryption logic). |
| Body Content Type | hidden | Internal property, defaults to "multipart-form-data" (not relevant for encryption). |
| Message | string | The plain text message you want to encrypt. Required. |
| Passphrase | string | The secret key used to encrypt the message. Required. |
Output
- The output is a JSON field containing the encrypted string (ciphertext) produced by AES encryption of the input message with the provided passphrase.
- Example output:
{ "json": "U2FsdGVkX1+...encryptedText..." } - No binary data is produced by this operation.
Dependencies
- crypto-js: Used internally for AES encryption.
- No external API calls or Opencell service interaction are required for this operation.
- No special n8n configuration or environment variables are needed for encryption.
Troubleshooting
Common issues:
- Missing Required Fields: If "Message" or "Passphrase" is not provided, the node will throw an error indicating missing required parameters.
- Weak Passphrase: Using a weak or short passphrase may compromise security; always use a strong, unpredictable passphrase.
- Incompatible Decryption: Only the same passphrase can decrypt the message. Losing or mistyping the passphrase will make decryption impossible.
Error messages and resolutions:
"Cannot read property 'message' of undefined": Ensure both "Message" and "Passphrase" fields are filled."Invalid passphrase"(on decryption): Make sure you use the exact same passphrase for decryption as was used for encryption.