Zep AI icon

Zep AI

AI Tool for interacting with Zep memory and knowledge graph. Provides operations to store/retrieve conversation memory, search knowledge graphs, and manage user context.

Actions9

Overview

The "Create Thread" operation in this node allows users to create a new conversation thread within the Zep AI platform. This is useful for initializing a distinct conversation context or session associated with a specific user. Creating threads helps organize conversations, track interactions, and manage memory or knowledge graph data related to that thread.

Common scenarios:

  • Starting a new chat session for a user in a chatbot application.
  • Organizing multiple parallel conversations by different users.
  • Preparing a thread context before adding messages or retrieving user context.

Practical example:
You have a customer support bot where each customer interaction should be tracked separately. When a new customer starts chatting, you use this operation to create a new thread with a unique thread ID and associate it with the customer's user ID. Subsequent messages and context retrievals will reference this thread.

Properties

Name Meaning
Thread ID Unique identifier for the conversation thread (e.g., thread-def456).
User ID The unique identifier of the user who owns or participates in the thread (e.g., user-123).

Output

The output JSON object includes:

  • success: Boolean indicating if the thread creation was successful.
  • threadId: The thread ID provided as input.
  • userId: The user ID provided as input.
  • threadCreated: The full response from the Zep API representing the created thread details.

This output confirms the thread has been created and provides any additional metadata returned by the API.

Dependencies

  • Requires an active connection to the Zep AI API service.
  • Needs an API key credential configured in n8n for authentication with the Zep API.
  • The base URL used is https://api.getzep.com.
  • The node uses HTTP POST requests to the /api/v2/threads endpoint.

Troubleshooting

  • Common issues:

    • Missing or invalid threadId or userId parameters will cause the API call to fail.
    • Network connectivity problems or incorrect API credentials can prevent successful communication with the Zep API.

  • Error messages:

    • If the API returns an error, it will be surfaced as a node execution error.
    • Errors related to authentication typically indicate misconfigured or missing API keys.
    • Validation errors may occur if the threadId or userId do not meet expected formats or are empty.

  • Resolution tips:

    • Ensure both Thread ID and User ID are provided and correctly formatted.
    • Verify the API key credential is set up properly in n8n.
    • Check network access to https://api.getzep.com.

Links and References

Discussion