Actions20
Overview
This node integrates with the Zep AI Memory Service, allowing users to manage various resources such as collections, documents, users, sessions, and memory data. Specifically, for the Document - List operation, it retrieves a list of documents within a specified collection.
Common scenarios where this node is beneficial include:
- Retrieving all documents stored in a particular collection for further processing or analysis.
- Automating workflows that require fetching document metadata or content from the Zep AI Memory Service.
- Integrating document management into broader automation pipelines, such as syncing documents with other systems or triggering actions based on document data.
Practical example:
- A user wants to fetch all documents from a "CustomerSupport" collection to analyze recent support tickets and generate reports automatically.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection whose documents you want to list. This is a required string input. |
Output
The output is a JSON array representing the list of documents retrieved from the specified collection. Each item in the array corresponds to a document object returned by the Zep AI Memory Service API.
The structure typically includes document identifiers, content summaries, metadata, and other relevant fields as provided by the service.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Zep AI Memory Service.
- The node uses the base URL and API key from the configured credentials to make HTTP requests.
- Proper network access to the Zep AI Memory Service endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect collection name may result in empty results or errors indicating the collection does not exist.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials accordingly.
- "Collection not found" or similar errors suggest the specified collection name is incorrect or the collection has not been created.
- JSON parsing errors might occur if metadata or other JSON inputs are malformed; ensure valid JSON syntax.
Links and References
- Zep AI Memory Service Documentation (for detailed API reference and usage)
- n8n documentation on HTTP Request Node (conceptual understanding of how API calls work in n8n)