Zep v3 icon

Zep v3

Interact with Zep Cloud v3 API

Actions44

Overview

The "Get Node" operation of the Zep node allows users to retrieve detailed information about a specific node within a knowledge graph managed by the Zep Cloud v3 API. This operation is useful when you want to fetch metadata or attributes associated with a particular node identified by its UUID.

Typical use cases include:

  • Fetching details of an entity or concept represented as a node in a knowledge graph.
  • Integrating node data into workflows for further processing or analysis.
  • Validating the existence and properties of nodes before performing updates or deletions.

For example, if you have a graph representing customer data, you can use this operation to get detailed information about a specific customer node by providing its UUID.

Properties

Name Meaning
Graph ID The unique identifier of the graph. Required for most operations but optional here.
UUID The universally unique identifier of the node to retrieve. This is required.

Output

The output JSON contains the full details of the requested node as returned by the Zep Cloud API. This typically includes all metadata, attributes, and relationships associated with the node.

The structure generally looks like this (example fields may vary):

{
  "uuid": "string",
  "name": "string",
  "type": "string",
  "metadata": { /* object with additional node info */ },
  "created_at": "ISO8601 timestamp",
  "updated_at": "ISO8601 timestamp",
  // other node-specific fields
}

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.
  • Network access to https://api.getzep.com must be available.

Troubleshooting

  • Missing UUID: The UUID property is required. If omitted, the node will throw an error indicating the missing parameter.
  • Invalid UUID: Providing an invalid or non-existent UUID will result in an API error stating that the node was not found.
  • Authentication errors: Ensure the API key credential is correctly set up and has permissions to access node data.
  • Network issues: Connectivity problems to the Zep API endpoint will cause request failures.
  • Graph ID usage: Although optional for this operation, specifying an incorrect Graph ID might lead to unexpected results or errors if used in other related operations.

Links and References

Discussion