Crypto module provides different encryption across workflows

Describe the issue/error/question

The crypto block in Cloud seems to use a different encryption key across my workflows, so I am not getting the same encrypted result each time. Can I control the encryption key? I am using SHA256 for all. This happened when I imported workflows from the Desktop version, but many have the same encryption result.

What is the error message (if any)?


Please share the workflow

Share the output returned by the last node

{ "message": "Incorrect password." }

Information on your n8n setup

  • n8n version: 0.210.2
  • Database you’re using (default: SQLite): default
  • Running n8n with the execution process [own(default), main]: default
  • Running n8n via [Docker, npm,, desktop app]:

Hi @bgschust, I am sorry to hear you’re having trouble.

I am not sure I can follow though.

Which data exactly is your Webhook node passing on to your Crypto node? Using mock data like below produces the same result both on n8n cloud and a local version of n8n:



In both cases the value of encryptedPassword is LCa0a2j/xo/5m0U8HTBBNBNCLXBkg7+g+YpeiGJm564=.

Perhaps you can share a few more details on how to reproduce your specific problem?

I’m not sure what else to tell you. All my other crypto nodes were consistent except one.

I am now encrypting with a code block and that works.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.