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 collections, documents, sessions, users, and memory data within the Zep platform. Specifically, for the Collection - Create operation, it enables creating a new collection by specifying its name, description, and optional metadata.

Common scenarios where this node is beneficial include:

  • Organizing AI memory or knowledge bases into named collections.
  • Structuring data for AI models that require segmented or categorized information.
  • Automating the creation of collections as part of a larger workflow managing AI memory or document storage.

Practical example:

  • Automatically create a new collection named "Customer Support Logs" with a description and metadata to store chat logs related to customer support interactions.

Properties

Name Meaning
Collection Name The name of the collection to be created.
Description A textual description of the collection, providing additional context or details.
Metadata Additional metadata as a JSON object to store custom key-value pairs associated with the collection.

Output

The node outputs a JSON object representing the response from the Zep API after creating the collection. This typically includes details about the newly created collection such as its name, description, metadata, and any other relevant identifiers or status information returned by the API.

No binary data output 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 the API key.
  • Network access to the Zep API endpoint is necessary.

Troubleshooting

  • Invalid or missing API key: The node will fail if the API key is not provided or invalid. Ensure the correct API key credential is configured.
  • Malformed JSON in Metadata: If the metadata JSON is incorrectly formatted, the request will fail. Validate JSON syntax before input.
  • Collection name conflicts: Attempting to create a collection with a name that already exists may result in an error from the API.
  • Network issues: Connectivity problems to the Zep API endpoint will cause request failures.
  • Error messages: The node returns error messages from the API in the output JSON under an error field when continueOnFail is enabled.

Links and References

Discussion