Actions100
- Activity Logs Actions
- Articles Actions
- 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
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation updates an existing Rack Storage entity by its unique identifier. It sends a PUT request to modify the rack storage's details such as location, name, description, dimensions, power capacity, timestamps, and company association. This is useful in scenarios where you need to maintain accurate and up-to-date information about physical rack storages in an inventory or asset management system.
Practical examples:
- Updating the maximum wattage capacity of a rack storage after hardware upgrades.
- Changing the location ID when a rack storage is moved to a different facility.
- Modifying descriptive fields like name or description to reflect new usage or status.
Properties
Name | Meaning |
---|---|
Id | The unique numeric identifier of the rack storage to update (required). |
Additional Body Fields | Optional additional fields to include in the update request body: |
- Id | Unique ID of the rack storage (number). |
- Location Id | Unique ID of the location where the rack storage is situated (number). |
- Name | Name of the rack storage (string). |
- Description | Description text for the rack storage (string). |
- Max Wattage | Maximum wattage capacity the rack storage can handle (number). |
- Starting Unit | Starting unit number of the rack storage (number). |
- Height | Height dimension of the rack storage (number). |
- Width | Width dimension of the rack storage (number). |
- Created At | Timestamp when the rack storage was created (string, date-time format). |
- Updated At | Timestamp when the rack storage was last updated (string, date-time format). |
- Discarded At | Timestamp when the rack storage was discarded; can be null if not discarded (string). |
- Company Id | Unique ID of the company associated with the rack storage (number). |
Output
The node outputs JSON data representing the updated rack storage object returned from the API after the PUT request. This typically includes all the properties of the rack storage, reflecting the current state after the update.
If the API supports binary data output, it would be summarized here, but based on the provided code and context, the output is purely JSON.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests.
- Depends on the external API endpoint that manages rack storage entities.
- The base URL for the API must be set in the node credentials or environment configuration.
Troubleshooting
- Invalid or missing Id: The update will fail if the "Id" property is not provided or does not correspond to an existing rack storage. Ensure the correct numeric ID is supplied.
- API authentication errors: If the API key or token is invalid or missing, the request will be rejected. Verify credential setup in n8n.
- Validation errors: Providing invalid data types or out-of-range values for fields like max wattage or dimensions may cause the API to return errors. Double-check field formats and constraints.
- Network issues: Connectivity problems to the API endpoint will prevent successful updates. Confirm network access and API availability.
Links and References
- Refer to your specific rack storage API documentation for detailed field descriptions and validation rules.
- n8n documentation on HTTP Request node for general API interaction patterns.
- Best practices for managing API credentials securely in n8n: Credentials Documentation.