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 sessions, users, collections, documents, and memory data via API calls. Specifically, for the Session - Update operation, it updates an existing session's details such as the associated user ID and additional metadata.

Common scenarios where this node is beneficial include:

  • Updating session information in a conversational AI or chatbot system to reflect changes in user association or session context.
  • Managing session metadata dynamically during workflows that require tracking or modifying session attributes.
  • Synchronizing session data between external systems and the Zep AI Memory Service.

Practical example:

  • After authenticating a user in a chatbot, you might update the session to associate it with the authenticated user's ID and add metadata like user preferences or session state.

Properties

Name Meaning
Session ID The unique identifier for the session to update.
User ID The user ID to associate with the session (optional; can be used to link a user to session).
Metadata Additional metadata as a JSON object to store extra information related to the session.

Output

The node outputs the JSON response returned by the Zep AI Memory Service after updating the session. This typically includes the updated session details such as session ID, associated user ID, and any stored metadata.

The output is structured as an array of JSON objects, each representing the result of the update operation for an input item.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Zep AI Memory Service.
  • The base URL for the Zep API and the API key must be configured in the node credentials.
  • Network access to the Zep AI Memory Service endpoint is necessary.

Troubleshooting

  • Invalid Session ID: If the session ID provided does not exist, the API may return an error indicating the session was not found. Verify the session ID is correct.
  • Authentication Errors: Missing or invalid API key will cause authentication failures. Ensure the API key credential is correctly set up.
  • Malformed Metadata JSON: The metadata property must be valid JSON. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
  • API Rate Limits or Network Issues: Temporary network problems or rate limiting by the API could cause request failures. Retry or check API usage limits.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.

Links and References

Discussion