Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Get User Episodes" operation of the Episode resource in this node allows you to retrieve all episodes associated with a specific user from the Zep Cloud v3 API. An episode typically represents an event or a piece of data linked to a user within a knowledge graph or interaction history.
This operation is useful when you want to analyze, display, or process all episodic data related to a particular user, such as their interactions, events, or recorded sessions. For example, you might use it to fetch all conversation episodes for a user to generate reports, perform sentiment analysis, or feed into other workflows.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose episodes you want to retrieve. This is optional but recommended to specify for filtering episodes by user. |
Output
The output JSON contains an array of episode objects retrieved from the API endpoint /api/v2/graph/episodes/user/{userId}. Each episode object typically includes details about the episode such as its unique identifier, type, content data, timestamps, and any metadata associated with it.
The node does not explicitly handle binary data for this operation; the output is purely JSON representing the episodes.
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/graph/episodes/user/{userId} - Proper configuration of the API key credential in n8n is necessary for successful authentication.
Troubleshooting
- Missing or invalid User ID: If the User ID is not provided or incorrect, the API may return an error or empty results. Ensure the User ID is correct and corresponds to an existing user.
- Authentication errors: If the API key credential is missing, expired, or invalid, the node will fail with authentication errors. Verify that the API key is correctly set up in n8n credentials.
- API rate limits or downtime: If the Zep Cloud API is unreachable or rate-limited, requests may fail. Check network connectivity and API status.
- Unexpected response format: If the API changes its response structure, the node's output may not match expectations. Review API documentation for updates.
Links and References
- Zep Cloud API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made in n8n)
This summary is based on static analysis of the node's source code and the provided input properties. It focuses specifically on the "Episode" resource and the "Get User Episodes" operation.