Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
This node allows you to update (PUT) a specific Rack Storage Item in the Hudu system via its API. It is designed for scenarios where you need to modify details of an existing rack storage item, such as changing its associated asset, updating its status, or modifying metadata like reserved messages or power specifications.
Common use cases:
- Updating the assignment or configuration of a rack storage slot in a data center inventory.
- Modifying asset information linked to a rack position.
- Changing operational parameters (e.g., power draw, status) for monitoring or compliance purposes.
Example:
You have a rack storage item representing a server slot, and you want to update its assigned asset, change its status to "reserved," and add a note about maintenance.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the Rack Storage Item that needs to be updated. |
| Additional Body Fields | Object | Optional collection of fields to update on the rack storage item. |
| └─ 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 updating the specified rack storage item. The structure of this output will typically reflect the updated state of the rack storage item, including all fields that were modified or are present in the resource.
Example output structure:
{
"id": 123,
"rack_storage_role_id": 5,
"asset_id": 42,
"start_unit": 1,
"end_unit": 2,
"status": 1,
"side": 0,
"max_wattage": 500,
"power_draw": 250,
"rack_storage_role_name": "Server",
"reserved_message": "Reserved for upgrade",
"rack_storage_role_description": "Primary server slot",
"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": 10
}
Note: Actual fields may vary depending on the API's response.
Dependencies
- External Service: Requires access to a Hudu instance with the API enabled.
- API Key/Credentials: Needs valid
avantguardHuduApicredentials configured in n8n, including the base URL and authentication token. - n8n Configuration: Ensure the credential named
avantguardHuduApiis set up in your n8n instance.
Troubleshooting
Common Issues:
- Invalid or missing credentials: If the API key or base URL is incorrect, the node will fail to authenticate.
- Resource not found: If the provided "Id" does not correspond to an existing rack storage item, the API may return a 404 error.
- Validation errors: Supplying invalid values (e.g., negative numbers for IDs, required fields missing) can result in 400 Bad Request errors.
- Permission denied: The API user may lack permission to update certain rack storage items.
Error Messages & Resolutions:
"401 Unauthorized": Check your API credentials and permissions."404 Not Found": Verify the "Id" property matches an existing rack storage item."400 Bad Request": Review input fields for correct types and required values.