Zep Chat Memory
Zep Chat Memory stores the message history of a conversation in Zep, a memory service for AI assistants, and retrieves it when needed. You can use Zep Cloud or a Zep server installed by your company. This way, components that answer questions take into account what was said before.
Each history is identified by a Session ID: messages with the same identifier form one conversation.
When to use it
- Your company already uses Zep and wants its assistants’ history stored there.
- You want conversation history kept in a service you can also query from other applications.
Configuration
Before you start you need the address of your Zep service and, if it asks for one, its access key.
| Field | What it does |
|---|---|
| Zep URL | The address of your Zep service. |
| API Key | The access key of your Zep service. |
Advanced options
| Field | What it does |
|---|---|
| API Base Path | The version of the service to talk to: api/v1 or api/v2. Use api/v2 with Zep Cloud and api/v1 with your own Zep server. Default: api/v1. |
| 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 give an agent memory, use for example Postgres Memory.
Example
The insurer Cobertia has an assistant that answers questions about its policies from the general terms and conditions:
- Add Zep Chat Memory, type the address of its Zep Cloud account in Zep URL and its key in API Key.
- In API Base Path, choose
api/v2, and connect the customer’s policy number to Session ID. - Connect Memory to the External Memory input of Retrieval QA History.
When a customer asks what their home insurance covers and then writes “and if it’s a water leak?”, the assistant understands they are still talking about that policy.
Good practices
- Use a different Session ID for each customer or case so histories don’t mix.
- If the component fails when the flow runs, check that API Base Path matches your type of Zep service.