Hudu icon

Hudu

Interact with Hudu REST API

Expiration → Get Many

AI-generated

Overview

This node operation retrieves multiple expiration records from the Hudu system. It supports filtering by various criteria such as company, expiration type, resource ID, and resource type. 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 item, reducing the risk of rate limiting issues. This operation is useful for scenarios where users need to fetch and process multiple expiration entries, such as monitoring asset warranties, SSL certificates, or domain expirations.

Use Case Examples

  1. Fetch all expiration records for a specific company to monitor upcoming asset warranties.
  2. Retrieve a limited number of SSL certificate expirations to check for renewals.
  3. Get all expiration records wrapped in a single item to efficiently process them in subsequent workflow steps without triggering rate limits.

Properties

Name Meaning
Return All Whether to return all expiration results or only up to a given limit.
Limit Maximum number of expiration 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 Filters to narrow down the expiration records by company, expiration type, resource ID, and resource type.

Output

JSON

  • items - Array of expiration records returned when results are wrapped in a single item.
  • count - Count of expiration records returned when results are wrapped in a single item.
    - Properties of individual expiration records returned as JSON objects.

Dependencies

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

Troubleshooting

  • Common issues include invalid or missing API credentials, resulting in authentication errors.
  • Incorrect filter values may lead to empty results or errors; ensure filters like company ID and resource type are valid.
  • If 'Return All' is false and 'Limit' is set too low, not all desired records will be retrieved.
  • Rate limiting errors may occur if results are not wrapped and downstream nodes process each item individually; use 'Wrap Results in Single Item' to mitigate this.

Discussion