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

This node integrates with the Zep AI platform to retrieve detailed user profile information by their unique user ID. The "Get User Info" operation fetches metadata, account details, and profile data associated with a specified user in Zep.

Typical use cases include:

  • Enriching workflows with user-specific data for personalization.
  • Auditing or monitoring user accounts within an AI-driven knowledge system.
  • Integrating user profile retrieval into larger automation pipelines that require user context.

For example, you might use this node to get the profile of a user identified as "user-123" to display their account details or to feed their metadata into another system.

Properties

Name Meaning
User ID The unique identifier of the user whose information you want to retrieve. This should be a string like "user-123" or any unique user ID.

Output

The output JSON contains:

  • userId: The user ID requested.
  • userInfo: An object containing the user's profile information, metadata, and account details as returned from the Zep API.
  • response: The full raw response from the Zep API call for further inspection or debugging.

Example output structure (simplified):

{
  "userId": "user-123",
  "userInfo": {
    // user profile fields such as name, email, metadata, etc.
  },
  "response": {
    // full API response object
  }
}

No binary data is output by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Zep AI API.
  • The node makes HTTP GET requests to the endpoint: https://api.getzep.com/api/v2/users/{userId}.
  • Ensure network access to the Zep API endpoint.
  • Proper permissions on the API key to read user information are necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID parameter will cause the request to fail.
    • Network connectivity problems or incorrect API credentials will result in authentication errors.
    • If the user ID does not exist, the API may return a 404 or empty response.

  • Error messages:

    • Errors thrown by the node typically come from failed HTTP requests. For example:
      • "Request failed with status code 401" indicates invalid or missing API credentials.
      • "Request failed with status code 404" means the user ID was not found.
    • To resolve, verify the User ID is correct, check API key validity, and ensure the node has proper permissions.

Links and References

Discussion