Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Get Entity Types" operation of the "Entity Type" resource in this node allows users to retrieve entity types from the Zep Cloud v3 API. This operation can fetch either all available entity types or user-specific entity types if a User ID is provided.
This node is beneficial when you want to programmatically access metadata about entity types defined in your knowledge graph or system, which can be used for further processing, filtering, or integration with other workflows.
Practical example:
- Fetching all entity types to display them in a UI dropdown for selection.
- Retrieving user-specific entity types to customize data processing or visualization based on user context.
Properties
| Name | Meaning |
|---|---|
| Graph ID | The unique identifier of the graph. Required for most operations but optional here. |
| User ID | Optional user identifier to get entity types specific to that user. |
Output
The output is a JSON array containing the entity types retrieved from the API. Each entity type object typically includes details such as the entity type's name and possibly other metadata describing it.
No binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Zep Cloud v3 API.
- The node makes HTTP GET requests to the endpoint
https://api.getzep.com/api/v2/entity-types. - No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Missing or invalid API credentials: The node will fail to authenticate. Ensure the API key credential is correctly configured in n8n.
- Invalid User ID or Graph ID: If provided, these must be valid identifiers recognized by the API; otherwise, the request may return empty results or errors.
- Network issues: Connectivity problems to the Zep API endpoint will cause request failures.
- Unexpected API response: If the API changes or returns unexpected data, the node might throw errors or produce incorrect outputs.
To resolve errors, verify credentials, input parameters, and network connectivity. Consult API documentation for any changes in endpoint behavior.
Links and References
- Zep Cloud API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)