> For the complete documentation index, see [llms.txt](https://docs.flowiseai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/memory/conversation-summary-memory.md).
# Conversation Summary Memory
Usa la tabla de base de datos `chat_message` de Flowise como mecanismo de almacenamiento para guardar/recuperar conversaciones.
Este tipo de memoria crea un breve resumen de la conversación a lo largo del tiempo. Esto es útil para acortar información de discusiones largas. Actualiza y guarda un resumen actual mientras la conversación continúa. Esto es especialmente útil en chats más largos, donde guardar cada mensaje anterior ocuparía demasiado espacio.
## Entrada
| Parámetro | Descripción | Valor por defecto |
| ---------- | --------------------------------------------------------------------------------------- | ----------------- |
| Chat Model | LLM usado para realizar la sumarización | |
| Session Id | Un ID para recuperar/almacenar mensajes. Si no se especifica, se usará un ID aleatorio. | |
| Memory Key | Una clave usada para formatear mensajes en la plantilla de prompt | chat\_history |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/memory/conversation-summary-memory.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
%20(1)%20(1)%20(1)%20(2).png?alt=media)