Actions44
- Edge Actions
- Entity Type Actions
- Episode Actions
- Graph Actions
- Node Actions
- Session Actions
- Thread Actions
- User Actions
Overview
The "Get Session Messages" operation of the Zep node allows you to retrieve messages associated with a specific session from the Zep Cloud v3 API. This is useful for scenarios where you want to fetch conversation history or message logs tied to a particular session identifier. For example, you might use this operation to display chat transcripts, analyze user interactions, or audit communication sessions.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the session whose messages you want to retrieve. |
| Limit | Maximum number of messages to return in one request (minimum 1). Defaults to 50. |
| Cursor | Optional pagination cursor to fetch subsequent pages of results (minimum 0). Defaults to 0. |
Output
The output JSON contains an array of message objects retrieved from the specified session. Each message typically includes details such as the role of the sender, the type of role, and the content of the message. This structured data can be used downstream in workflows for display, processing, or analysis.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential configured for authenticating with the Zep Cloud v3 API.
- The node makes HTTP requests to
https://api.getzep.comendpoints. - Proper network connectivity to the Zep API service is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Session ID will cause the API call to fail.
- Exceeding rate limits imposed by the Zep API may result in errors.
- Pagination issues if the cursor value is incorrect or out of range.
Error Messages:
- Errors returned from the API are surfaced with their message text.
- If the node throws an error about unknown operations, verify that the Resource is set to "Session" and Operation to "Get Session Messages".
- Authentication errors indicate problems with the API key credential setup.
Resolutions:
- Ensure the Session ID is correct and exists in your Zep account.
- Check API key validity and permissions.
- Use the Limit and Cursor parameters properly to paginate through large message sets.
Links and References
- Zep Cloud API Documentation (for detailed API endpoint info)
- n8n Documentation on Creating Custom Nodes
- General guidance on Handling Pagination in APIs