Actions20
Overview
This node integrates with the Zep AI Memory Service to manage collections, documents, users, sessions, and memory data. Specifically, for the Document - Add operation, it allows you to add a new document to a specified collection within the Zep service. This is useful when you want to programmatically store or update textual content in a structured collection, such as adding knowledge base articles, user-generated content, or any other document-type data.
Practical examples include:
- Adding new support articles to a documentation collection.
- Uploading transcripts or notes into a session-specific document repository.
- Storing user-generated content or logs for later retrieval and analysis.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection where the document will be added. |
| Document ID | The unique identifier for the document being added. |
| Content | The textual content of the document to be stored. |
| Metadata | Additional metadata as a JSON object to associate with the document (optional). |
Output
The node outputs a JSON array representing the response from the Zep API after adding the document. This typically includes details about the newly created document such as its ID, content, associated collection, and any metadata stored.
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: Ensure that the API key credential is correctly configured and valid.
- Collection not found: Verify that the specified collection name exists before adding a document.
- Malformed JSON in Metadata: If providing metadata, ensure it is valid JSON; otherwise, parsing errors may occur.
- Duplicate Document ID: Using an existing document ID might cause conflicts; use unique identifiers.
- Network issues: Check connectivity to the Zep API endpoint if requests time out or fail.
Common error messages usually come from the API response and indicate authentication failures, invalid parameters, or resource not found errors. Reviewing the exact API response message helps resolve these issues.
Links and References
- Zep AI Memory Service Documentation (general reference for API endpoints and usage)
- n8n Documentation on Creating Custom Nodes