Opencell

Overview

The Cryptography → Decrypt Message operation in this n8n node allows you to decrypt a message that was previously encrypted using AES encryption. This is useful for workflows where sensitive data needs to be securely transmitted or stored and later retrieved in its original, readable form.

Common scenarios:

• Decrypting confidential information received from another system or user.
• Automating the processing of encrypted files or messages within secure business processes.
• Integrating with other systems that require encrypted payloads for compliance or security reasons.

Practical example:
Suppose you receive an encrypted string via email or API. You can use this node to decrypt the message using the correct passphrase and then process the plaintext further in your workflow.

---

Properties

Name	Type	Meaning
Authentication	options	Selects the authentication method for Opencell API (not used for decryption itself).
Body Content Type	hidden	Always set to "multipart-form-data" (not relevant for decryption logic).
Encrypted Message	string	The AES-encrypted string to be decrypted.
Passphrase	string	The secret key/passphrase used to decrypt the message; must match the one used to encrypt.

---

Output

• The output is a single field containing the decrypted message as a UTF-8 string.
• Example output:

  {
    "json": "Decrypted message content"
  }
  

• If decryption fails (e.g., wrong passphrase or corrupted input), the output will be an empty string.

---

Dependencies

• crypto-js: Used internally for AES decryption.
• No external API keys or services are required for the decryption operation itself.
• Node authentication properties are present but not used for cryptography operations.

---

Troubleshooting

Common issues:

• Incorrect passphrase: If the passphrase does not match the one used for encryption, the output will be an empty string.
• Malformed encrypted message: If the input is not a valid AES-encrypted string, decryption will fail and return an empty string.
• Empty output: Indicates either a wrong passphrase or invalid/corrupted encrypted data.

Error messages:

• The node does not throw explicit errors for decryption failures; it simply returns an empty string. Check your passphrase and input data if you get no result.

---

Links and References

• crypto-js AES documentation
• n8n Documentation
• AES Encryption & Decryption Explained