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 a specific Rack Storage Item by its ID from the AvantGuard Hudu system. It is useful in scenarios where you need to fetch detailed information about a particular storage item, such as for inventory management, auditing, or integration with other systems that require up-to-date storage data.
Practical Example:
You might use this node in an automation workflow to look up the details of a rack storage item when given its unique identifier, perhaps as part of a larger process to update asset records or generate reports.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the requested Rack Storage Item. This is required. |
Output
The node outputs a JSON object containing the details of the requested Rack Storage Item. The exact structure depends on the API response, but typically includes fields such as the item's ID, name, location, and other relevant metadata.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- Credentials: Needs an n8n credential named
avantguardHuduApiwith at least abaseUrlproperty configured. - Environment: The base URL for the API must be set in the credentials.
Troubleshooting
Missing or Invalid Credentials:
If the required credentials are not provided or are incorrect, the node will fail to connect to the AvantGuard Hudu API. Ensure theavantguardHuduApicredential is properly configured in n8n.Invalid ID Provided:
Supplying an ID that does not exist may result in an error or an empty response. Double-check the ID value before running the workflow.API Connectivity Issues:
Network problems or incorrect base URL configuration can cause connection errors. Verify network access and the correctness of the API endpoint.