Zep Memory icon

Zep Memory

Interact with Zep AI Memory Service
Join our community

Actions20

Overview

This node integrates with the Zep AI Memory Service, allowing users to manage various resources such as collections, documents, memories, sessions, and users. Specifically, for the Collection - Get operation, it retrieves detailed information about a named collection from the Zep service.

Typical use cases include:

  • Fetching metadata and details of a specific collection to understand its contents or configuration.
  • Integrating collection data into workflows that require knowledge of existing collections before performing further actions like adding documents or querying memory.
  • Automating management tasks by programmatically accessing collection information.

For example, a user might want to get the description and metadata of a collection named "CustomerInteractions" to decide whether to add new documents or update existing ones.

Properties

Name Meaning
Collection Name The name of the collection to retrieve. This is a required string input specifying which collection's details to fetch.

Output

The node outputs JSON data representing the collection's details as returned by the Zep API. This typically includes fields such as the collection's name, description, metadata, creation date, and other relevant attributes defined by the service.

The output is structured as an array of JSON objects, each corresponding to one input item processed. Each object contains the collection information under the json property.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Zep AI Memory Service.
  • Needs the base URL of the Zep API, provided via credentials.
  • The node makes HTTP requests to the Zep API endpoints to perform operations.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Specifying a non-existent collection name will likely result in a "not found" error from the API.
    • Malformed JSON in optional metadata fields (not applicable here but relevant for other operations) can cause request failures.

  • Error messages:

    • "Unauthorized" or similar indicates problems with API credentials; verify the API key and permissions.
    • "Collection not found" means the specified collection name does not exist; check spelling and existence.
    • Network errors suggest connectivity issues; ensure the node can reach the Zep API endpoint.

  • Resolution tips:

    • Double-check the collection name input for typos.
    • Confirm API key validity and scope.
    • Test connectivity to the Zep API outside n8n if needed.

Links and References

Discussion