MongoDB 聊天内存节点#
¥MongoDB Chat Memory node
使用 MongoDB Chat Memory 节点将 MongoDB 用作 memory 服务器来存储聊天历史记录。
¥Use the MongoDB Chat Memory node to use MongoDB as a memory server for storing chat history.
本页列出了 MongoDB Chat Memory 节点支持的操作列表以及更多资源的链接。
¥On this page, you'll find a list of operations the MongoDB Chat Memory node supports, and links to more resources.
Parameter resolution in sub-nodes
Sub-nodes behave differently to other nodes when processing multiple items using an expression.
Most nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five name values, the expression {{ $json.name }} resolves to each name in turn.
In sub-nodes, the expression always resolves to the first item. For example, given an input of five name values, the expression {{ $json.name }} always resolves to the first name.
节点参数#
¥Node parameters
- 会话密钥:输入用于存储工作流数据中内存的键。
¥Session Key: Enter the key to use to store the memory in the workflow data.
- 收藏名称:输入用于存储聊天记录的集合名称。如果集合不存在,系统将创建该集合。
¥Collection Name: Enter the name of the collection to store the chat history in. The system will create the collection if it doesn't exist.
- 数据库名称:输入用于存储聊天记录的数据库名称。如果未提供,则将使用凭据中的数据库。
¥Database Name: Enter the name of the database to store the chat history in. If not provided, the database from credentials will be used.
- 上下文窗口长度:输入要作为上下文参考的先前交互次数。
¥Context Window Length: Enter the number of previous interactions to consider for context.
相关资源#
¥Related resources
有关服务的更多信息,请参阅 LangChain 的 MongoDB 聊天消息历史记录文档。
¥Refer to LangChain's MongoDB Chat Message History documentation for more information about the service.
View n8n's Advanced AI documentation.
单内存实例#
¥Single memory instance
If you add more than one MongoDB 聊天内存 node to your workflow, all nodes access the same memory instance by default. Be careful when doing destructive actions that override existing memory contents, such as the override all messages operation in the Chat Memory Manager node. If you want more than one memory instance in your workflow, set different session IDs in different memory nodes.