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 - Create operation, it allows you to create a new session by providing a unique session ID, optionally associating it with a user ID, and attaching additional metadata.

Common scenarios where this node is beneficial include:

  • Creating and managing conversational sessions in AI chatbots or virtual assistants.
  • Tracking user interactions over time by associating sessions with user IDs.
  • Storing contextual metadata about sessions for analytics or personalized experiences.

For example, you might use this node to start a new chat session when a user initiates a conversation, linking that session to the user's identity and storing relevant session details.

Properties

Name Meaning
Session ID The unique identifier for the session. This is required to create a new session.
User ID The user ID to associate with the session. Optional; links the session to a specific user.
Metadata Additional metadata as a JSON object. Can store any extra information related to the session.

Output

The node outputs a JSON object representing the created session as returned by the Zep AI Memory Service API. This typically includes the session ID, associated user ID (if provided), metadata, timestamps, and other session-related details.

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 AI Memory Service endpoint is necessary.

Troubleshooting

  • Invalid or missing Session ID: The session ID is required. Ensure it is provided and unique.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Malformed metadata JSON: If providing metadata, ensure it is valid JSON; otherwise, the request may fail.
  • Network issues: Check connectivity to the Zep API endpoint if requests time out or fail.
  • API errors: The node forwards error messages from the API. Review these messages for hints on misconfiguration or invalid parameters.

If the node is set to continue on failure, errors will be included in the output JSON under an error field for each failed item.

Links and References

Discussion