Zep v3

Overview

The "Get User Node" operation of the Zep node allows you to retrieve detailed information about a specific user node from the Zep Cloud v3 API. This operation is useful when you want to fetch metadata or structured data associated with a particular user in your knowledge graph or system managed by Zep.

Typical use cases include:

• Fetching user profile details or attributes stored as a node.
• Integrating user-specific data into workflows for personalization or analytics.
• Accessing user-related nodes to build or update graphs or threads related to that user.

For example, if you have a user ID and want to get the corresponding user node's data (such as connections, properties, or other metadata), this operation will query the Zep API and return that information.

Properties

This property is required and must be provided to specify which user's node data should be fetched.

Output

The output of this operation is a JSON object representing the user node data retrieved from the Zep API endpoint /api/v2/users/{userId}/node. The structure typically includes all relevant fields describing the user node, such as identifiers, attributes, relationships, and metadata as defined by the Zep service.

No binary data output is involved in this operation.

Dependencies

• Requires an active connection to the Zep Cloud v3 API.
• Requires an API key credential configured in n8n for authentication with the Zep API.
• The node uses HTTP requests with authentication to communicate with the Zep API endpoints.

Troubleshooting

• Common issues:

  • Invalid or missing User ID: Ensure the User ID is correctly specified and exists in the Zep system.
  • Authentication errors: Verify that the API key credential is properly set up and has sufficient permissions.
  • Network or connectivity problems: Check internet access and API availability.

• Error messages:

  • "Unknown user operation: getNode": This would indicate a misconfiguration of the operation parameter; ensure "Get User Node" is selected.
  • HTTP errors from the API (e.g., 404 Not Found): Usually means the user node does not exist or the User ID is incorrect.
  • JSON parsing errors: Could occur if the response is malformed; check API status or contact support.

Resolving these usually involves verifying input parameters, credentials, and network conditions.

Links and References

• Zep Cloud API Documentation (for detailed API endpoint descriptions)
• n8n documentation on HTTP Request with Authentication