Hudu icon

Hudu

Interact with Hudu REST API

Relation → Get Many

AI-generated

Overview

This node operation retrieves multiple relation records from the Hudu API. It supports filtering relations based on origin and destination entity IDs and types, as well as whether the relation is inverse. Users can choose to return all results or limit the number of results returned. Additionally, results can be wrapped into a single item containing an array of items and a count, which helps prevent downstream nodes from executing once per result and potentially hitting rate limits. This operation is useful for scenarios where you need to fetch and process multiple relations between entities in Hudu, such as asset relationships or company connections.

Use Case Examples

  1. Fetch all relations where the origin entity is a specific asset and the destination entity is a user.
  2. Retrieve up to 50 relations filtered by entity types to analyze connections between different entity categories.
  3. Return all relations wrapped in a single item to efficiently process them downstream without triggering rate limits.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return when 'Return All' is false.
Wrap Results in Single Item Whether to return all results as a single item with an 'items' array and 'count' field to prevent downstream nodes from executing once per result, which can cause rate limiting issues.
Filters Filters to apply client-side to the relations, including origin entity ID and type, destination entity ID and type, and whether the relation is inverse. Note that filtering is applied client-side and may impact performance.

Output

JSON

  • items - Array of relation objects when results are wrapped in a single item.
  • count - Number of relation objects returned when results are wrapped.

Dependencies

  • Hudu REST API
  • API key credential for authentication

Troubleshooting

  • If the node returns an error stating the resource is not known, ensure the resource parameter is set to 'relations'.
  • Client-side filtering may impact performance; consider limiting the number of results or refining filters to improve efficiency.
  • If rate limiting issues occur downstream, enable 'Wrap Results in Single Item' to reduce the number of executions.

Discussion