Actions20
Overview
The node integrates with the Zep AI Memory Service, enabling interaction with various resources such as users, sessions, collections, documents, and memory. Specifically, for the Memory - Add operation, it allows adding an array of message objects to a session's memory. This is useful in scenarios where you want to maintain or update conversational context by appending new messages to an existing session memory.
Practical examples include:
- Chatbot applications that store conversation history incrementally.
- AI assistants that need to remember previous interactions within a session.
- Systems that log user-assistant exchanges for later retrieval or analysis.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier for the session to which messages will be added. |
| Messages | An array of message objects, each containing a role (e.g., "user" or "assistant") and content (the message text). |
Example of Messages property value:
[
{ "role": "user", "content": "Hello" },
{ "role": "assistant", "content": "Hi there!" }
]
Output
The node outputs JSON data representing the response from the Zep AI Memory Service after adding messages to the session memory. The output structure corresponds to the API's response format, typically confirming the successful addition of messages or providing details about the updated memory state.
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
Common issues:
- Invalid or missing session ID can cause the API request to fail.
- Malformed JSON in the
Messagesproperty may lead to parsing errors. - Authentication failures if the API key is incorrect or expired.
- Network connectivity problems preventing access to the Zep service.
Error messages and resolutions:
"Unauthorized"or"Authentication failed": Verify the API key credential is correct and has proper permissions."Invalid session ID"or"Session not found": Ensure the session ID exists and is correctly specified."Malformed JSON": Check that theMessagesinput is valid JSON and follows the expected structure.- Timeout or network errors: Confirm network connectivity and that the Zep service is reachable.
Links and References
- Zep AI Memory Service Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes