AvantGuard - HuduInstall

Overview

The Put Rack Storages Id operation for the "Rack Storages" resource allows you to update an existing rack storage entry by its unique identifier. This node is typically used in scenarios where you need to modify details of a rack storage, such as its name, location, dimensions, or status within an inventory or asset management system.

Practical examples:

• Updating the name or description of a rack storage after a physical move.
• Changing the maximum wattage or dimensions due to hardware upgrades.
• Marking a rack storage as discarded or updating its timestamps.

Properties

Name	Type	Meaning
Id	Number	The unique identifier of the rack storage to update. (Required)
Additional Body Fields	Collection	Optional fields to include in the request body when updating the rack storage.
└─ Id	Number	The unique ID of the rack storage. (Usually matches the main Id property)
└─ Location Id	Number	The unique ID of the location associated with the rack storage.
└─ Name	String	The name of the rack storage.
└─ Description	String	A description of the rack storage.
└─ Max Wattage	Number	The maximum wattage the rack storage can handle.
└─ Starting Unit	Number	The starting unit number of the rack storage.
└─ Height	Number	The height of the rack storage.
└─ Width	Number	The width of the rack storage.
└─ Created At	String	The creation date and time of the rack storage.
└─ Updated At	String	The last updated date and time of the rack storage.
└─ 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 that owns the rack storage.

Output

The node outputs a json object representing the updated rack storage. The structure will generally reflect the properties sent in the request, including all updated fields. Example output:

{
  "id": 123,
  "location_id": 45,
  "name": "Main Server Rack",
  "description": "Upgraded to support new servers.",
  "max_wattage": 2000,
  "starting_unit": 1,
  "height": 42,
  "width": 24,
  "created_at": "2023-01-01T12:00:00Z",
  "updated_at": "2024-06-10T09:30:00Z",
  "discarded_at": null,
  "company_id": 7
}

Note: The actual output fields depend on the API response and may include additional metadata.

Dependencies

• External Service: Requires access to the AvantGuard Hudu API.
• API Credentials: You must configure the avantguardHuduApi credential in n8n, which should include the base URL and authentication details.
• n8n Configuration: Ensure the credentials are set up under the name avantguardHuduApi.

Troubleshooting

Common Issues:

• Missing or Invalid Id: If the required "Id" property is missing or does not correspond to an existing rack storage, the API will likely return a "Not Found" or "Invalid ID" error.
• Authentication Errors: Incorrect or missing API credentials will result in authentication failures.
• Validation Errors: Providing invalid data types or omitting required fields in "Additional Body Fields" may cause the API to reject the request.

Error Messages & Resolutions:

• "401 Unauthorized": Check your API credentials in n8n.
• "404 Not Found": Verify the "Id" value corresponds to an existing rack storage.
• "400 Bad Request": Review the input fields for correct data types and required values.

Links and References

• n8n Documentation
• AvantGuard Hudu API Documentation (if available)
• OpenAPI Specification Reference