Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
This node operation "Get Entity Edges for a Node" interacts with the Zep Cloud v3 API to retrieve all entity edges associated with a specific node identified by its UUID. It is useful in scenarios where you want to explore or analyze relationships (edges) connected to a particular node within a knowledge graph or data graph managed by Zep.
Practical examples include:
- Fetching all relationships of a customer node in a customer interaction graph.
- Retrieving connections of an entity in a semantic knowledge base.
- Analyzing linked data around a specific concept or object in a graph database.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier (UUID) of the node whose entity edges you want to retrieve. This is a required string input. |
Output
The output JSON contains the list of entity edges related to the specified node. Each edge typically represents a relationship or connection between entities in the graph. The exact structure depends on the Zep API response but generally includes details such as edge identifiers, types, source and target nodes, and possibly metadata about the relationship.
No binary data output is involved in this operation.
Dependencies
- Requires an active API key credential for authenticating requests to the Zep Cloud v3 API.
- The node must be configured with this API key credential under the generic name "zepApi".
- Network access to https://api.getzep.com is necessary.
Troubleshooting
- Missing or invalid UUID: Ensure the UUID property is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network issues: Confirm connectivity to the Zep API endpoint.
- API rate limits or server errors: Handle errors gracefully; consider enabling "Continue On Fail" in n8n to avoid workflow interruption.
- Common error messages from the API will be propagated; check the message content for clues (e.g., "Not Found" if the node UUID does not exist).
Links and References
- Zep Cloud API Documentation (general reference for API endpoints)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)
Additional Notes on Implementation (Static Analysis)
- The operation calls the endpoint
GET /api/v2/graph/node/{uuid}/entity-edges. - The UUID parameter is retrieved via
this.getNodeParameter("uuid", e). - The HTTP request uses authentication via the configured API key credential.
- The response is returned as JSON and passed downstream in the workflow.