Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
This node integrates with the Zep Cloud v3 API to interact with various resources such as users, threads, graphs, nodes, edges, episodes, entity types, and sessions. Specifically, for the "Node" resource and the "Get Episodes for a Node" operation, it retrieves all episodes associated with a particular node identified by its UUID.
Use cases include:
- Fetching historical or contextual episodes related to a specific node in a knowledge graph.
- Analyzing events or interactions linked to a node for insights or further processing.
- Integrating episode data into workflows that require context around entities represented by nodes.
Example: Given a node UUID representing a customer, you can retrieve all episodes (events or interactions) related to that customer to analyze their history or behavior.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier (UUID) of the node for which to retrieve episodes. This is a required string input. |
Output
The output is a JSON array containing the episodes associated with the specified node. Each item in the array represents an episode object as returned by the Zep Cloud API. The structure typically includes details about the episode's content, type, timestamps, and any metadata provided by the API.
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 requests to
https://api.getzep.comendpoints. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing UUID parameter will cause the API request to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network connectivity issues preventing access to the Zep Cloud API endpoint.
Error messages:
"Unknown node operation: getEpisodes": Indicates the operation name might be misspelled or unsupported.- HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) usually indicate credential problems or invalid UUIDs.
Resolutions:
- Ensure the UUID is correctly provided and corresponds to an existing node.
- Verify the API key credential is valid and has appropriate permissions.
- Check network connectivity and firewall settings.
Links and References
- Zep Cloud API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Authentication for setting up API credentials