Hudu icon

Hudu

Interact with Hudu REST API

Asset → Get Many

AI-generated

Overview

This node operation retrieves multiple asset records from the Hudu system based on specified filters and parameters. It is useful for scenarios where users need to fetch a list of assets, optionally filtered by criteria such as archived status, asset layout, company, ID, name, serial number, slug, or update date. The node supports returning all results or limiting the number of results, and can wrap the results in a single item to optimize downstream processing.

Use Case Examples

  1. Fetch all assets belonging to a specific company.
  2. Retrieve up to 25 assets that have been updated in the last 7 days.
  3. Get archived assets with a specific asset layout.
  4. Return all assets as a single item with a count and items array to avoid rate limiting in subsequent nodes.

Properties

Name Meaning
Return All Determines whether to return all matching asset results or limit the number of results.
Limit Specifies the maximum number of asset results to return when 'Return All' is false.
Wrap Results in Single Item If enabled, returns all results as a single JSON item containing an 'items' array and a 'count' field. This helps prevent downstream nodes from executing once per result item, which can reduce rate limiting issues.
Filters A collection of filters to narrow down the assets returned. Filters include archived status, asset layout, company, asset ID, name, primary serial number, search query, slug, and updated date range.

Output

JSON

  • items - An array of asset objects returned when 'Wrap Results in Single Item' is enabled.
  • count - The total number of assets returned when results are wrapped in a single item.
  • * - Individual asset objects with their respective properties when results are not wrapped.

Dependencies

  • Requires an API key credential for Hudu REST API access.

Troubleshooting

  • If no assets are returned, verify that the filter criteria are correct and that assets exist matching those filters.
  • If the node throws an error about an unknown resource, ensure the resource parameter is set to 'assets'.
  • Rate limiting issues may occur if many individual asset items are returned; enabling 'Wrap Results in Single Item' can help mitigate this.
  • Ensure the API credentials are valid and have sufficient permissions to access asset data.

Discussion