Skip to content

Redis 聊天内存节点#

¥Redis Chat Memory node

使用 Redis 聊天内存节点将 Redis 用作 memory 服务器。

¥Use the Redis Chat Memory node to use Redis as a memory server.

本页列出了 Redis Chat Memory 节点支持的操作列表以及更多资源的链接。

¥On this page, you'll find a list of operations the Redis Chat Memory node supports, and links to more resources.

Credentials

你可以在 此处 中找到此节点的身份验证信息。

¥You can find authentication information for this node here.

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.

  • 会话生存时间:使用此参数使会话在指定秒数后过期。

¥Session Time To Live: Use this parameter to make the session expire after a given number of seconds.

  • 上下文窗口长度:输入要作为上下文参考的先前交互次数。

¥Context Window Length: Enter the number of previous interactions to consider for context.

模板和示例#

¥Templates and examples

Template widget placeholder.

相关资源#

¥Related resources

有关服务的更多信息,请参阅 LangChain 的 Redis Chat Memory 文档

¥Refer to LangChain's Redis Chat Memory documentation for more information about the service.

View n8n's Advanced AI documentation.

单内存实例#

¥Single memory instance

If you add more than one Redis 聊天内存 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.