AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node for n8n allows users to interact with the Hudu API, specifically to retrieve ("Get") items stored in rack storage. This is useful for IT asset management, data center operations, or any scenario where you need to programmatically query and filter rack storage inventory from Hudu.

Common scenarios:

• Listing all items currently stored in a specific rack.
• Filtering rack storage items by asset, role, status, or time range (created/updated).
• Integrating Hudu rack storage data into automated workflows for reporting, auditing, or monitoring.

Practical example:
Automatically fetch all rack storage items updated in the last week and send a summary report via email.

---

Properties

Name	Type	Meaning
Additional Query Parameters	collection	Optional set of filters to refine which rack storage items are returned. Each field below can be used individually or in combination: Rack Storage Role Id (number): Filter by specific rack storage role. Asset Id (number): Filter by associated asset ID. Start Unit (number): Filter by starting unit position in the rack. End Unit (number): Filter by ending unit position in the rack. Status (number): Filter by item status. Side (string): Filter by side of the rack (e.g., "Front" or "Rear"). Created At (string): Filter by creation date/time. Accepts ISO 8601 format. Can specify a range (start_datetime,end_datetime), an exact match, or open-ended ranges (e.g., 2023-06-07T12:34:56Z,). Updated At (string): Filter by last update date/time. Same format as "Created At".

---

Output

• The node outputs a list of rack storage items matching the specified filters.
• Each output item appears in the json field and typically includes details such as:
  • Item ID
  • Asset ID
  • Rack Storage Role ID
  • Start/End Unit
  • Status
  • Side
  • Created At / Updated At timestamps
  • Other metadata as provided by the Hudu API

Example output structure:

{
  "id": 123,
  "asset_id": 456,
  "rack_storage_role_id": 789,
  "start_unit": 1,
  "end_unit": 4,
  "status": 1,
  "side": "Front",
  "created_at": "2023-06-01T12:00:00Z",
  "updated_at": "2023-06-05T15:30:00Z"
}

Note: Actual fields may vary depending on the Hudu API response.

• Binary Data: This node does not output binary data; all output is JSON.

---

Dependencies

• External Service: Requires access to a Hudu instance with API enabled.
• API Key/Credentials: Needs valid credentials configured in n8n under the name avantguardHuduApi. The base URL for your Hudu instance must be set in these credentials.
• n8n Configuration: No special configuration beyond credentials is required.

---

Troubleshooting

Common issues:

• Invalid Credentials: If the API key or base URL is incorrect, authentication errors will occur. Double-check your credential settings in n8n.
• Missing Required Permissions: The API user must have permission to read rack storage items.
• Incorrect Date Format: For "Created At" and "Updated At" filters, ensure dates are in ISO 8601 format. Invalid formats may result in no data or errors.
• No Results Returned: If filters are too restrictive, the query may return an empty list. Try broadening your search criteria.

Common error messages:

• "401 Unauthorized": Check your API key and permissions.
• "400 Bad Request": Likely due to invalid query parameters or date formats.
• "404 Not Found": The resource does not exist or the endpoint is incorrect.

---

Links and References

• Hudu API Documentation
• n8n Documentation: Creating Workflows
• ISO 8601 Date Format Reference