The idea is:
-
Maybe we can have a “Secret” Node where we can store some data that will be en-/decrypted in the database and thus on the filesystem.
-
Have the possibility to set “Contains sensitive data” in the “Settings” for certain nodes so N8N knows that must store it’s contents encrypted
My use case:
While trying to successfully recreate HMAC signing for a new connector that is not yet supported out of the box there is now way to secretly store you credential in the community version. The only way to get around this is creating a package and require the package is a community package to store the data secretly.
Hereby I share and example of a workflow with takes INPUT(request to server) and create OUTPUT(response from server) using an HTTP Request without the need of an external code to make this possible.
I think it would be beneficial to add this because:
The keys must be set given in the workflow, meaning they will not be encrypted like credentials.
Any resources to support this?
Are you willing to work on this?
I did some testing, see screenshot