How to set a key and value in a hashmap using Redis node?

How do I mention the name of the hashmap to which i need to set the key and the value?

Information on your n8n setup

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

Hey @reev,

My understanding would be that you would do the same thing you would from the Redis CLI so key would be your key and value would be the field names and values you want to set so it would be something like the below.

Hi @Jon
I did update it to the provided format but it has set the field with some weird order of the value.

Kindly refer the screen shot to understand how the field and value are stored

Hey @reev,

That looks like a fix I did last year might still be needed, I always thought maybe it was just being used incorrectly as there were not many reports of it.

I will remake the PR and create a dev ticket for it now that I am on the n8n side :slight_smile:

1 Like

ok sure.
Kindly update when you have it live.

1 Like

Hey @Jon!

Just wondering if there was any resolution to this?

I’ve had a wee bit of a peek around the forums and this looks like something a couple of people have experienced ( albeit, rarely! it is very niche :slight_smile: )

Here’s what that looks like for me:


Hey @ilya,

I was actually talking to @RicardoE105 about this one a while ago and a possible fix I put in place, It turns out it can be used by passing in an object. I don’t remember the exact details and I forgot to make a note of it but I will have another play later this week to try and remember.

Hey Jon!
Thanks for your help on this.

As you can see, I’ve tried to follow this route, without success.
Running JSON.stringify on it beforehand also sadly doesn’t get us anywhere (just spits out that whacky array from earlier)

Let me know what you think!

New version [email protected] got released which includes the GitHub PR 5832.

i still have the same problem. using version 0.236.2.

Hey @anas,

Can you share an example of what you are doing so I can give it a test? 0.236 is pretty old now as well so I would recommend upgrading when you get a chance.