AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node for n8n allows users to create new rack storage records in the Hudu system by performing the "Post Rack Storages" operation. This is useful for automating infrastructure management tasks, such as registering new physical or virtual rack storage units, updating inventory systems, or integrating with other IT asset management workflows.

Practical examples:

• Automatically add a new rack storage entry when provisioning hardware.
• Sync rack storage data from another system into Hudu.
• Batch-create multiple rack storage records based on external triggers or schedules.

Properties

Name	Type	Meaning
Additional Body Fields	collection	Optional fields to include in the request body when creating a rack storage.
└ Id	number	The unique ID of the rack storage.
└ Location Id	number	The unique ID of the location of the rack storage.
└ Name	string	The name of the rack storage.
└ Description	string	The description of the rack storage.
└ Max Wattage	number	The maximum wattage the rack storage can handle.
└ Starting Unit	number	The starting unit of the rack storage.
└ Height	number	The height of the rack storage.
└ Width	number	The width of the rack storage.
└ Created At	string	The date and time when the rack storage was created.
└ Updated At	string	The date and time when the rack storage was last updated.
└ Discarded At	string	The date and time when the rack storage was discarded. Can be null.
└ 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 record. The structure typically includes details of the newly created rack storage, such as its ID, name, location, and any other provided fields.

Example output:

{
  "id": 123,
  "location_id": 45,
  "name": "Rack A1",
  "description": "Main server rack",
  "max_wattage": 2000,
  "starting_unit": 1,
  "height": 42,
  "width": 19,
  "created_at": "2024-06-01T12:00:00Z",
  "updated_at": "2024-06-01T12:00:00Z",
  "discarded_at": null,
  "company_id": 7
}

Note: The actual output fields depend on the Hudu API's response.

Dependencies

• External Service: Requires access to a Hudu instance with API enabled.
• API Key/Credentials: Needs valid avantguardHuduApi credentials configured in n8n, including the base URL and authentication token.
• n8n Configuration: Ensure the node is properly installed and the credentials are set up in your n8n instance.

Troubleshooting

Common issues:

• Authentication errors: If credentials are missing or incorrect, the node will fail to connect to the Hudu API. Double-check the API key and base URL.
• Missing required fields: If mandatory fields (such as name or location_id) are not provided, the API may return validation errors.
• Invalid data types: Supplying values in the wrong format (e.g., string instead of number) can cause request failures.
• Network issues: Connectivity problems between n8n and the Hudu API endpoint can result in timeouts or connection errors.

Error messages and resolutions:

• "401 Unauthorized": Check your API credentials and permissions.
• "400 Bad Request": Review the input fields for missing or invalid data.
• "404 Not Found": Verify the base URL and endpoint configuration.

Links and References

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