Hudu icon

Hudu

Interact with Hudu REST API

Actions100

Overview

This node operation retrieves multiple rack storage records from the Hudu system. It is designed to fetch a list of rack storages with optional filtering and pagination controls. This is useful in scenarios where you need to bulk query rack storage data for inventory management, auditing, or integration with other systems.

Practical examples include:

  • Fetching all rack storages belonging to a specific company.
  • Retrieving rack storages created or updated within a certain date range.
  • Limiting the number of rack storages returned for performance reasons.
  • Filtering rack storages by physical attributes such as height or width.

Properties

Name Meaning
Return All Whether to return all matching rack storage results or only up to a specified limit.
Limit The maximum number of rack storage results to return when "Return All" is false. Must be at least 1.
Filters A collection of filters combined using AND logic to narrow down the rack storages returned. These include:
  Company Name or ID Filter rack storages by associated company, selectable from a list or by specifying an ID.
  Created At Filter by creation date with modes: exact date, date range, or preset ranges (e.g., last 7 days, this month).
  Height Filter by rack height (numeric value).
  Location ID Filter by location identifier (numeric value).
  Max Width Filter by maximum rack width (numeric value).
  Min Width Filter by minimum rack width (numeric value).
  Updated At Filter by update date with modes similar to Created At (exact date, date range, preset ranges).

Output

The output is a JSON array where each element represents a rack storage record matching the query parameters. Each record includes detailed fields describing the rack storage's properties such as identifiers, dimensions, associated company, location, creation and update timestamps, and any other relevant metadata provided by the Hudu API.

If the node supports binary data output (not indicated here), it would typically represent attachments or images related to rack storages, but this operation focuses on JSON data retrieval.

Dependencies

  • Requires an active connection to the Hudu REST API.
  • Needs an API key credential configured in n8n for authentication.
  • The base URL for the Hudu API must be set in the node credentials.
  • No additional external services are required beyond the Hudu API.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key will cause authentication failures.
    • Using invalid filter values (e.g., non-existent company IDs) may result in empty responses.
    • Exceeding rate limits imposed by the Hudu API can cause request failures.
    • Setting "Return All" to true with very large datasets might lead to timeouts or memory issues.

  • Error Messages:

    • Authentication errors usually indicate problems with the API key or permissions.
    • Validation errors may occur if filter parameters are malformed or out of expected ranges.
    • Network errors suggest connectivity issues between n8n and the Hudu API endpoint.

  • Resolutions:

    • Verify API key correctness and permissions.
    • Double-check filter inputs and use valid IDs or date formats.
    • Implement retry logic or reduce data volume by using filters and limits.
    • Ensure network access to the Hudu API base URL.

Links and References

Discussion