Zep

Feature availability

The Zep node is deprecated from n8n 1.108.0. Refer to Deprecated and versioned nodes for more information.

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

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

Credentials

Refer to the Zep credentials documentation for authentication information for this node.

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 ID: Enter the ID to use to store the memory in the workflow data.

Templates and examples

Browse Zep node documentation integration templates or search all templates

Related resources

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.