Zep Memory icon

Zep Memory

Interact with Zep AI Memory Service

Actions12

Overview

The node integrates with the Zep AI Memory Service, allowing users to manage memory data related to AI sessions. Specifically for the Memory - Get operation, it retrieves stored memory messages associated with a particular session ID. This is useful in scenarios where you want to fetch the conversation history or context that an AI assistant has retained during a session.

Practical examples include:

  • Retrieving past interactions of a user session to provide context-aware responses.
  • Debugging or auditing what information the AI has stored for a session.
  • Feeding previous conversation data into another system or workflow step.

Properties

Name Meaning
Session ID The unique identifier for the session whose memory you want to retrieve.

Output

The output JSON contains the memory data retrieved from the Zep AI Memory Service for the specified session. This typically includes an array of message objects representing the conversation history or stored memory entries for that session.

The structure generally looks like this (example):

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

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Zep AI Memory Service.
  • The node makes HTTP requests to the Zep service base URL configured via credentials.
  • Proper network access to the Zep API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing session ID will result in errors or empty responses.
    • Incorrect or expired API key will cause authentication failures.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Errors returned from the API are passed through; typical messages might indicate "Not Found" if the session ID does not exist.
    • Authentication errors will mention invalid token or unauthorized access.

  • Resolutions:

    • Verify the session ID is correct and exists in the Zep system.
    • Ensure the API key credential is valid and has proper permissions.
    • Check network settings and firewall rules to allow outbound requests to the Zep API.

Links and References

Discussion