Zep v3

Overview

The "Get Graph" operation of the Zep node allows users to retrieve detailed information about a specific knowledge graph stored in the Zep Cloud v3 API. This operation is useful when you want to fetch metadata and current state of a graph, such as its name, description, fact rating instructions, and other properties.

Typical use cases include:

• Inspecting an existing graph before performing updates or analyses.
• Retrieving graph details for display or reporting purposes.
• Integrating graph data retrieval into automated workflows that depend on graph metadata.

For example, a user might want to get the details of a customer interaction graph to verify its configuration or to pull its description for documentation.

Properties

Output

The output of the "Get Graph" operation is a JSON object representing the graph's details as returned by the Zep Cloud API. It typically includes fields such as:

• graph_id: Unique identifier of the graph.
• name: The name of the graph.
• description: A textual description of the graph.
• fact_rating_instruction: Optional instructions related to fact rating within the graph.
• Other metadata fields relevant to the graph's configuration and status.

The output is structured as a JSON array with one item per input item processed, each containing the graph information.

No binary data is output by 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.
• Network access to https://api.getzep.com must be available.

Troubleshooting

• Missing or invalid Graph ID: If the Graph ID parameter is empty or incorrect, the API call will fail. Ensure the Graph ID is correctly specified.
• Authentication errors: If the API key credential is missing or invalid, requests will be rejected. Verify the API key setup in n8n credentials.
• Network issues: Connectivity problems to the Zep API endpoint can cause failures. Check network access and proxy settings if applicable.
• API rate limits: Excessive requests may trigger rate limiting by the Zep API. Implement retry logic or reduce request frequency if needed.

Common error messages:

• "Unknown graph operation: get": Indicates the operation name was not recognized; ensure "get" is selected as the operation.
• HTTP 404 Not Found: The specified Graph ID does not exist.
• HTTP 401 Unauthorized: Authentication failed due to invalid or missing API key.

Links and References

• Zep Cloud API Documentation (for detailed API endpoints and parameters)
• n8n Documentation (for general usage of custom nodes and credentials)

This summary is based solely on static analysis of the provided source code and property definitions.