Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Delete Edge" operation of the Zep node allows users to delete a specific edge from a knowledge graph managed by the Zep Cloud v3 API. An edge represents a relationship or connection between two nodes (entities) in the graph. This operation is useful when you want to remove outdated, incorrect, or irrelevant relationships from your graph data.
Typical use cases include:
- Cleaning up or maintaining the integrity of a knowledge graph by removing obsolete connections.
- Managing dynamic data where relationships between entities change over time.
- Automating graph updates as part of a larger workflow that modifies graph structure.
For example, if your graph models employee relationships and an employee leaves the company, you might delete edges representing their current projects or team memberships.
Properties
| Name | Meaning |
|---|---|
| graphId | The unique identifier of the graph. Optional for this operation but often used to specify the graph context. |
| uuid | The UUID of the edge to delete. This is required and uniquely identifies the edge within the graph. |
Output
The output JSON contains the response from the Zep Cloud API after attempting to delete the specified edge. Typically, this will confirm successful deletion or provide error details if the operation failed.
The structure generally includes:
- Confirmation of deletion status.
- Possibly metadata about the deleted edge or related information.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Zep Cloud v3 API.
- The node makes HTTP requests to
https://api.getzep.comendpoints. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent UUID will result in an error indicating the edge was not found.
- Missing the required
uuidproperty will cause the node to fail before making the API call. - Network or authentication errors if the API key is missing, invalid, or expired.
Error Messages:
"Unknown edge operation: delete": Indicates the operation parameter was incorrectly set; ensure it is exactly "delete".- API errors returned from Zep Cloud will be passed through, such as 404 Not Found if the edge UUID does not exist.
Resolutions:
- Verify the UUID corresponds to an existing edge.
- Ensure the API key credential is correctly configured and has sufficient permissions.
- Check network connectivity and endpoint availability.
Links and References
- Zep Cloud API Documentation (for detailed API reference)
- n8n Documentation (for general usage of custom nodes and credentials)