Redis chat memory has different shape than window buffer memory and can't be used as drop in replacement

[Morriz]

Bug Description

Redis chat memory is NOT a drop-in replacement for the memory buffer, even though we may assume it is (what else is the point of making such abstractions). We should surely be able to swap a memory connector without killing our app, no?

To Reproduce

1. create chat app with window buffer memory
2. swap for Redis chat memory
3. @n8n/chat client does not work anymore

Expected behavior

Memory connectors to have the same signature and output shape

Operating System

docker

n8n Version

1.66.0

Node.js Version

docker

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @Morriz,

We have created an internal ticket to look into this which we will be tracking as "GHC-440"

[Morriz]

Sooooo disappointed....I can cry

[Joffcom]

@Morriz the instructions are unclear, I have made a chat app with Window Buffer Memory nothing fancy

I have then loaded my chat URL and sent it a question to which it replied, All is good.

I then swapped out the Window Buffer Memory with a Redis Chat Memory

Set the credential and asked a question and it was all good.

What is the error you are actually seeing?

Also after yesterdays comments please keep in mind our code of conduct which you can find here: https://github.com/n8n-io/n8n/blob/master/CODE_OF_CONDUCT.md