Actions20
Overview
This node integrates with the Zep AI Memory Service to manage documents within collections. Specifically, the Delete Document operation allows users to remove a document from a specified collection by providing the collection name and the unique document ID.
Common scenarios where this node is beneficial include:
- Cleaning up outdated or irrelevant documents from a knowledge base.
- Managing document lifecycle in an AI memory system by removing entries that are no longer needed.
- Automating document management workflows where documents need to be deleted based on certain triggers or conditions.
For example, if you have a collection of user manuals stored as documents, and a manual becomes obsolete, you can use this node to delete that specific document from the collection automatically.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection from which the document will be deleted. |
| Document ID | The unique identifier of the document to delete within the specified collection. |
Output
The output of this node is a JSON object representing the response from the Zep AI Memory Service after attempting to delete the document. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the API response data related to the delete operation.
This node does not output binary data.
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 service and a valid API key.
- Network access to the Zep AI Memory Service endpoint is necessary.
Troubleshooting
Common Issues:
- Providing an incorrect collection name or document ID will result in failure to find and delete the document.
- Missing or invalid API key credentials will cause authentication errors.
- Network connectivity issues may prevent the node from reaching the Zep service.
Error Messages:
- Errors returned from the API (e.g., "Document not found") will be included in the node's output if "Continue On Fail" is enabled.
- Authentication errors typically indicate invalid or missing API keys; verify credentials in the node settings.
- JSON parsing errors may occur if metadata or other JSON inputs are malformed.
To resolve these issues:
- Double-check the collection name and document ID values.
- Ensure the API key credential is correctly configured and has appropriate permissions.
- Verify network connectivity and endpoint accessibility.
Links and References
- Zep AI Memory Service Documentation (for detailed API usage and authentication)
- n8n Documentation on Creating Custom Nodes