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
The AvantGuard - Hudu node for n8n allows users to retrieve a list of rack storage records from the Hudu API. The "Get Rack Storages" operation fetches rack storage data, optionally filtered by various parameters such as company, location, dimensions, and creation or update timestamps. This node is useful in scenarios where you need to automate inventory management, synchronize asset information, or generate reports on physical rack storage assets within your organization.
Practical examples:
- Automatically pull all rack storages for a specific company or location into a spreadsheet.
- Filter and retrieve only those racks created or updated within a certain time window for auditing purposes.
- Integrate with other systems to keep track of available rack space based on width and height filters.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Query Parameters | collection | Optional query parameters that can be added to filter the results. Contains the following options: |
| └ Company Id | number | Filter by company id. Only rack storages belonging to the specified company will be returned. |
| └ Location Id | number | Filter by location id. Only rack storages at the specified location will be returned. |
| └ Height | number | Filter by rack height. Only racks matching the specified height will be included. |
| └ Min Width | number | Filter by minimum rack width. Only racks with a width greater than or equal to this value will be included. |
| └ Max Width | number | Filter by maximum rack width. Only racks with a width less than or equal to this value will be included. |
| └ Created At | string | Filter rack storages created within a range or at an exact time. Format: 'start_datetime,end_datetime' for range, 'exact_datetime' for exact match. Both values should be in ISO 8601 format. If only one value is provided, it acts as an open-ended filter (from start until now, or from past until end). Examples: '2023-06-07T12:34:56Z,', ',2023-06-07T12:34:56Z', '2023-06-01T12:34:56Z,2023-06-07T12:34:56Z'. |
| └ Updated At | string | Filter rack storages updated within a range or at an exact time. Same format and logic as "Created At". |
Output
The node outputs a JSON array of rack storage objects. Each object represents a rack storage record retrieved from the Hudu API. The structure of each object typically includes fields such as:
{
"id": 123,
"company_id": 456,
"location_id": 789,
"height": 42,
"width": 19,
"created_at": "2023-06-01T12:34:56Z",
"updated_at": "2023-06-07T12:34:56Z",
// ...other rack storage properties
}
Note: The actual fields may vary depending on the Hudu API schema.
The node does not output binary data.
Dependencies
- External Service: Requires access to the Hudu API.
- API Credentials: You must configure the
avantguardHuduApicredential in n8n, which should include the base URL (baseUrl) and any necessary authentication details. - n8n Configuration: Ensure the credentials are set up in the n8n instance under the appropriate name.
Troubleshooting
Missing or Invalid Credentials:
Error message: "No credentials found" or "Invalid API key"
Resolution: Make sure theavantguardHuduApicredential is correctly configured in n8n with the correct base URL and authentication details.Incorrect Query Parameter Format:
Error message: "Invalid date format" or "Bad request"
Resolution: Ensure that date/time filters like "Created At" and "Updated At" use ISO 8601 format and follow the required syntax (e.g.,'start_datetime,end_datetime').No Results Returned:
Possible causes: Filters are too restrictive, or there are no matching records.
Resolution: Try removing or relaxing some filters to broaden the search.API Connection Issues:
Error message: "Network error" or "Failed to connect"
Resolution: Check network connectivity and verify that the Hudu API endpoint is accessible from your n8n instance.
Links and References
- Hudu API Documentation (for detailed field descriptions and API behavior)
- n8n Documentation: Creating and Using Credentials
- ISO 8601 Date and Time Format