Redis Chat Memory
Redis Chat Memory stores the message history of a conversation in a Redis server owned by your company and retrieves it when needed. This way, components that answer questions take into account what was said before, and the history stays on your server.
Each history is identified by a Session ID: messages with the same identifier form one conversation.
When to use it
- Your company already uses Redis and wants its assistants’ history stored there.
- Your data policy requires conversations to be stored on your own server.
- You want to share a conversation’s history with other applications that read from that server.
Configuration
Before you start you need a Redis server that NappAI can reach and a credential of the Redis API service with its connection address. See Credentials.
| Field | What it does |
|---|---|
| Credential (required) | The credential of the Redis API service. Pick one with Choose an option or create one with Add new credential. |
Advanced options
| Field | What it does |
|---|---|
| Session ID | The identifier of the history. Type it or connect it, for example to the customer number. Conversations with the same Session ID share their history. |
Output
Memory is the conversation history. Connect it to the External Memory input of Retrieval QA History, which reads the history before answering and saves each question and answer to it, or of Chat Memory, which reads the stored messages to use them elsewhere in the flow. If you connect it to Chat Memory, the Session ID of Chat Memory is used.
It does not connect to the Memory input of agents. To store an agent’s memory in Redis, use Redis Memory.
Example
Gimnasios Olmo has an assistant that answers questions about timetables and fees from its internal documentation:
- Create a Redis API credential with the address of the company’s Redis server.
- Add Redis Chat Memory, choose that credential and connect the member number to Session ID.
- Connect Memory to the External Memory input of Retrieval QA History.
When a member asks about the yoga class and then writes “and on Saturdays?”, the assistant understands they are still talking about yoga.
Good practices
- Use a different Session ID for each customer or case so histories don’t mix.