Hudu icon

Hudu

Interact with Hudu REST API

Asset Password → Get Many

AI-generated

Overview

This node operation retrieves multiple asset passwords from the Hudu system. It supports filtering by various criteria such as archived status, company, name, search query, slug, and update date range. Users can choose to return all results or limit the number of results, and optionally wrap the results in a single item containing an array and count. This operation is useful for scenarios where bulk retrieval of asset passwords is needed, such as auditing, reporting, or synchronization tasks.

Use Case Examples

  1. Retrieve all asset passwords updated in the last 7 days for a specific company.
  2. Get up to 25 asset passwords that match a search query and are not archived.
  3. Fetch asset passwords and wrap the results in a single item to avoid rate limiting in downstream nodes.

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 item, which can cause rate limiting issues.
Filters Collection of filters to narrow down the asset passwords retrieved, including archived status, company ID or name, name, search query, slug, and updated date range.

Output

JSON

  • items - Array of asset password objects returned by the operation when results are wrapped.
  • count - Number of asset password items returned when results are wrapped.
    - Individual asset password properties when results are returned as separate items.

Dependencies

  • Requires Hudu API credentials for authentication.

Troubleshooting

  • Common issues include invalid or missing API credentials, resulting in authentication errors.
  • Incorrect filter parameters may lead to no results or unexpected results; verify filter values and formats.
  • If 'Return All' is false and limit is set too low, not all desired results will be returned; adjust the limit accordingly.
  • When wrapping results, downstream nodes expecting individual items may not function as intended; ensure compatibility.

Discussion