Zep Memory

Overview

This node integrates with the Zep AI Memory Service to manage conversational memory associated with sessions. Specifically, the Memory - Add operation allows you to add an array of message objects (each containing a role and content) to a session's memory. This is useful for building or updating the context of a conversation over time, enabling AI assistants or chatbots to maintain stateful interactions.

Common scenarios:

• Storing user-assistant conversation history during a chat session.
• Adding new messages dynamically as a conversation progresses.
• Enhancing AI responses by providing relevant past messages from memory.

Example:
You have a chatbot that interacts with users in sessions. After each user input and assistant response, you use this node to add those messages to the session memory, so future queries can consider the full conversation context.

Properties

The Messages property expects JSON formatted like:

[
  { "role": "user", "content": "Hello" },
  { "role": "assistant", "content": "Hi there!" }
]

Output

The node outputs the response from the Zep AI Memory Service after adding the messages. The output is a JSON object representing the updated memory state or confirmation of the addition.

• The json output field contains the API response parsed into JSON.
• No binary data is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the Zep AI Memory Service.
• The node configuration must include the base URL of the Zep API and a valid API key.
• Network access to the Zep API endpoint is necessary.

Troubleshooting

• Invalid Session ID: If the session ID does not exist or is malformed, the API may return an error. Ensure the session ID is correct and the session has been created beforehand.
• Malformed Messages JSON: The messages property must be valid JSON and follow the expected structure. Invalid JSON or missing required fields (role, content) will cause errors.
• Authentication Errors: Missing or invalid API key will result in authorization failures. Verify the API key credential is correctly configured.
• API Endpoint Issues: Network problems or incorrect base URL settings can cause request failures. Confirm the base URL matches the Zep service endpoint.

If the node throws errors, check the error message returned in the output JSON for clues and verify all inputs and credentials.

Links and References

• Zep AI Memory Service Documentation (example placeholder link)
• n8n HTTP Request Node Documentation (for understanding underlying request mechanics)

This summary focuses on the Memory - Add operation of the Zep Memory node based on the provided source code and properties.