Zep v3 icon

Zep v3

Interact with Zep Cloud v3 API

Actions44

Overview

This node operation "Get Messages of a Thread" allows you to retrieve messages from a specific conversation thread stored in the Zep Cloud v3 API. It is useful for scenarios where you want to fetch historical chat or message data associated with a particular thread ID, such as displaying conversation history, analyzing chat content, or integrating thread messages into other workflows.

Practical examples include:

  • Fetching the last 50 messages of a customer support chat thread to display in a dashboard.
  • Retrieving paginated messages from a discussion thread for sentiment analysis.
  • Integrating thread messages into CRM or helpdesk systems for context enrichment.

Properties

Name Meaning
Thread ID The unique identifier of the thread from which to retrieve messages.
Limit Maximum number of messages to return (minimum 1). Defaults to 50.
Cursor Optional pagination cursor to specify the starting point for fetching messages (min 0).

Output

The output is a JSON array containing the messages retrieved from the specified thread. Each item in the array represents a message object as returned by the Zep Cloud API endpoint /api/v2/threads/{threadId}/messages. The structure typically includes fields such as message content, role, timestamps, and any metadata provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Zep Cloud v3 API.
  • The node uses HTTP requests to the base URL https://api.getzep.com.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Thread ID will cause the API request to fail.
    • Exceeding the maximum allowed limit or providing invalid cursor values may result in errors.
    • Network or authentication failures can prevent successful API calls.

  • Error messages:

    • "Unknown thread operation: getMessages": Indicates the operation name was not recognized; ensure the correct operation is selected.
    • API errors related to authorization usually indicate invalid or expired API credentials.
    • Pagination errors may occur if the cursor value is out of range or improperly formatted.

  • Resolutions:

    • Verify that the Thread ID is correct and exists in your Zep Cloud account.
    • Check that the API key credential is valid and has appropriate permissions.
    • Use valid numeric values for Limit and Cursor parameters.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion