AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node for n8n enables users to interact with the "Rack Storage Items" resource in the Hudu system. Specifically, the Post Rack Storage Items operation allows you to create new rack storage items by sending detailed information about each item to the Hudu API. This is useful for automating asset management workflows, such as registering new hardware in a data center, updating inventory records, or integrating asset tracking with other business processes.

Practical examples:

• Automatically add new servers or network devices to your rack inventory when they are provisioned.
• Integrate with procurement systems to register assets as soon as they arrive.
• Batch update rack storage details from spreadsheets or other sources.

---

Properties

Name	Type	Meaning
Additional Body Fields	collection	Optional body fields that can be added to the request.
└ Id	number	The unique ID of the rack storage item.
└ Rack Storage Role Id	number	The unique ID of the rack storage role.
└ Asset Id	number	The unique ID of the asset.
└ Start Unit	number	The start unit of the rack storage item.
└ End Unit	number	The end unit of the rack storage item.
└ Status	number	The status of the rack storage item.
└ Side	number	The side of the rack storage item.
└ Max Wattage	number	The maximum wattage of the rack storage item.
└ Power Draw	number	The power draw of the rack storage item.
└ Rack Storage Role Name	string	The name of the rack storage role.
└ Reserved Message	string	The reserved message for the rack storage item.
└ Rack Storage Role Description	string	The description of the rack storage role.
└ Rack Storage Role Hex Color	string	The hex color of the rack storage role.
└ Asset Name	string	The name of the asset.
└ Asset Url	string	The URL of the asset.
└ Url	string	The URL of the rack storage item.
└ Company Id	number	The unique ID of the company.

---

Output

The node returns the JSON response from the Hudu API after creating a rack storage item. The structure of the output will typically reflect the created item's properties, including all fields sent in the request and any additional metadata provided by the API (such as timestamps or internal IDs).

Example output structure:

{
  "id": 123,
  "rack_storage_role_id": 5,
  "asset_id": 42,
  "start_unit": 1,
  "end_unit": 4,
  "status": 1,
  "side": 0,
  "max_wattage": 500,
  "power_draw": 200,
  "rack_storage_role_name": "Server",
  "reserved_message": "",
  "rack_storage_role_description": "Main server role",
  "rack_storage_role_hex_color": "#FF0000",
  "asset_name": "Dell R740",
  "asset_url": "https://assets.example.com/42",
  "url": "https://hudu.example.com/rack-storage-items/123",
  "company_id": 2,
  // ...other possible fields returned by the API
}

Note: The actual output may include additional fields depending on the Hudu API's response.

---

Dependencies

• External Service: Requires access to a Hudu instance with the API enabled.
• API Key/Credentials: Needs valid credentials configured in n8n under the name avantguardHuduApi.
• Environment Variable: The base URL for the Hudu API must be set in the credentials (baseUrl).

---

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 Fields: If required fields are not provided in "Additional Body Fields," the API may reject the request. Ensure all necessary information is included.
• Field Type Mismatch: Providing a string where a number is expected (or vice versa) can cause validation errors.
• API Connectivity Issues: Network problems or incorrect base URLs can prevent successful communication with the Hudu API.

Common error messages:

• "401 Unauthorized": Check your API key and permissions.
• "400 Bad Request": Review the input fields for missing or invalid values.
• "404 Not Found": Verify the endpoint and resource identifiers.

---

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• AvantGuard GitHub