Skip to content

Zep 节点#

¥Zep node

Deprecated

此节点已弃用,将在未来的版本中移除。

¥This node is deprecated, and will be removed in a future version.

使用 Zep 节点将 Zep 用作 memory 服务器。

¥Use the Zep node to use Zep as a memory server.

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

¥On this page, you'll find a list of operations the Zep 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

  • 会话 ID:输入用于存储工作流数据中内存的 ID。

¥Session ID: Enter the ID to use to store the memory in the workflow data.

模板和示例#

¥Templates and examples

Template widget placeholder.

相关资源#

¥Related resources

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

¥Refer to LangChain's Zep documentation for more information about the service.

View n8n's Advanced AI documentation.

单内存实例#

¥Single memory instance

If you add more than one Zep 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.