Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Delete Thread" operation in the Zep node allows users to delete a specific conversation thread from the Zep Cloud v3 API. This is useful for managing and cleaning up threads that are no longer needed or relevant, such as removing outdated conversations or sensitive information.
Typical use cases include:
- Automatically deleting threads after a certain period or event.
- Managing user data privacy by removing conversation history on request.
- Cleaning up test or temporary threads created during development or testing.
For example, if you have a thread identified by its unique Thread ID and want to remove it from your system, this operation will send a deletion request to the Zep API to permanently remove that thread.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The unique identifier of the thread to be deleted. This is a required string property. |
Output
The output of the "Delete Thread" operation is the JSON response returned by the Zep API after attempting to delete the specified thread. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
The structure generally includes status information about the deletion request. No binary data is involved in this operation.
Example output (conceptual):
{
"success": true,
"message": "Thread deleted successfully"
}
or in case of failure:
{
"error": "Thread not found"
}
Dependencies
- Requires an active connection to the Zep Cloud v3 API.
- Requires an API key credential configured in n8n for authentication with the Zep API.
- The base URL used for requests is
https://api.getzep.com. - The node uses HTTP DELETE method to call the endpoint
/api/v2/threads/{threadId}.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Thread ID will result in an error indicating the thread could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Network issues or API downtime can prevent successful deletion.
Error Messages:
"Thread not found": Verify the Thread ID is correct and the thread exists.- Authentication errors: Check that the API key credential is correctly set up and has necessary permissions.
"Unknown thread operation: delete": This would indicate a misconfiguration in the node's operation parameter; ensure "Delete Thread" is selected.
Resolution Tips:
- Double-check the Thread ID input for typos.
- Confirm API credentials are valid and have access rights.
- Test connectivity to the Zep API endpoint outside n8n to rule out network issues.
Links and References
- Zep Cloud API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes
- HTTP methods overview: MDN Web Docs - HTTP Methods
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.