Zep Memory icon

Zep Memory

Interact with Zep AI Memory Service

Actions12

Overview

This node integrates with the Zep AI Memory Service to manage sessions, users, and memory data. Specifically, for the Session - List operation, it retrieves a list of all existing sessions from the Zep service.

Common scenarios where this node is useful include:

  • Retrieving active or historical sessions for analysis or monitoring.
  • Displaying session lists in dashboards or workflows.
  • Automating session management tasks based on session data.

For example, you might use this node to fetch all sessions and then filter or process them further in your workflow to identify sessions that need attention or archival.

Properties

Name Meaning
Session ID The unique identifier for the session (required for operations other than list)

Note: For the List operation on the Session resource, no additional input properties are required.

Output

The output is a JSON array representing the list of sessions retrieved from the Zep AI Memory Service. Each item in the array corresponds to a session object with its associated details as returned by the API.

The node does not output binary data.

Example output structure (simplified):

[
  {
    "session_id": "string",
    "user_id": "string",
    "metadata": { "key": "value" },
    "created_at": "timestamp",
    ...
  },
  ...
]

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

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network issues: Verify connectivity to the Zep API base URL.
  • Empty results: Confirm that there are existing sessions in the Zep service; otherwise, the list will be empty.
  • JSON parsing errors: If metadata or other JSON fields are malformed in inputs (for other operations), ensure they are valid JSON strings.

If the node throws errors related to request failures, check the error message for HTTP status codes and messages from the Zep API to diagnose issues such as invalid parameters or rate limits.

Links and References

Discussion