Actions44
- Graph Actions
- Edge Actions
- Entity Type Actions
- Episode Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Clone Graph" operation in the Zep node allows users to create a duplicate of an existing knowledge graph by specifying its unique identifier. This is useful when you want to replicate a graph's structure and data for testing, backup, or branching purposes without affecting the original graph.
Practical scenarios include:
- Creating a sandbox copy of a production graph to experiment with changes.
- Backing up a graph before performing bulk updates.
- Duplicating a graph to create variations for different projects or teams.
Properties
| Name | Meaning |
|---|---|
| Graph ID | The unique identifier of the graph to be cloned. This is required to specify which graph to duplicate. |
Output
The output JSON contains the response from the API after cloning the graph. Typically, this includes details about the newly created cloned graph such as its new unique identifier and metadata confirming the clone operation was successful.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Zep Cloud v3 API.
- The node makes HTTP POST requests to the endpoint
https://api.getzep.com/api/v2/graph/clonewith the graph ID in the request body. - Proper network connectivity to the Zep Cloud API is necessary.
Troubleshooting
- Missing Graph ID: If the Graph ID is not provided or invalid, the API will likely return an error indicating that the graph to clone could not be found. Ensure the correct Graph ID is supplied.
- Authentication Errors: If the API key credential is missing or invalid, authentication errors will occur. Verify that the API key is correctly configured in n8n credentials.
- API Rate Limits or Downtime: Temporary failures may happen due to rate limits or service outages. Retry after some time or check the service status.
- Unexpected API Response: If the API response format changes or contains errors, the node might throw exceptions. Review the error message and consult Zep API documentation.
Links and References
- Zep Cloud API Documentation (for detailed API endpoints and parameters)
- n8n Documentation on HTTP Request Node (for understanding how HTTP requests are made within n8n)
This summary focuses specifically on the "Clone Graph" operation under the "Graph" resource as requested.