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 retrieves information about a specific Rack Storage by its ID from the AvantGuard Hudu API. It is useful in scenarios where you need to fetch detailed data for a particular rack storage unit, such as inventory management, asset tracking, or integration with other IT infrastructure systems.
Practical Example:
You might use this node in an automation workflow to look up details of a rack storage when given its unique ID, perhaps as part of a larger process that audits or updates hardware assets.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the requested rack storage. This is required and uniquely identifies which rack storage record to retrieve. |
Output
The node outputs a JSON object containing the details of the requested rack storage. The exact structure depends on the API response, but typically includes fields such as the rack storage's ID, name, location, and other relevant metadata.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Credentials: Needs valid credentials (
avantguardHuduApi) configured in n8n, including thebaseUrlfor the Hudu instance. - n8n Configuration: Ensure the credentials are set up in n8n under the appropriate credential type.
Troubleshooting
- Invalid or Missing ID: If the provided "Id" does not exist, the node may return an error or an empty result. Double-check the ID value.
- Authentication Errors: If credentials are missing or incorrect, you may see errors related to authentication (e.g., "401 Unauthorized"). Make sure your API key and base URL are correct.
- Connection Issues: Network problems or incorrect base URL can cause connection failures. Verify connectivity to the Hudu API endpoint.