AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

The "Get Rack Storages" operation retrieves a list of rack storage entities from an external system, optionally filtered by various criteria such as company, location, dimensions, and creation or update timestamps. This node is useful in scenarios where you need to query and analyze rack storage data for inventory management, space planning, or reporting purposes.

For example, you might use this node to:

  • Fetch all rack storages belonging to a specific company or location.
  • Retrieve racks within certain size constraints (height or width).
  • Get racks created or updated within a particular date range to monitor recent changes.

Properties

Name Meaning
Additional Query Parameters Optional filters to narrow down the rack storages returned. You can specify any combination of the following:
Company Id: Filter by company identifier (number).
Location Id: Filter by location identifier (number).
Height: Filter by rack height (number).
Min Width: Filter by minimum rack width (number).
Max Width: Filter by maximum rack width (number).
Created At: Filter by creation timestamp or range (ISO 8601 string). Format examples:
 - Exact datetime: "2023-06-07T12:34:56Z"
 - Range: "2023-06-01T12:34:56Z,2023-06-07T12:34:56Z"
 - Open-ended ranges supported.
Updated At: Filter by last update timestamp or range (ISO 8601 string), same format as Created At.

Output

The node outputs JSON data representing the list of rack storages matching the specified filters. Each item in the output array corresponds to a rack storage entity with its associated properties as provided by the external API.

If the external API supports binary data related to rack storages (e.g., images or documents), the node would include it accordingly, but based on the provided code and properties, the output focuses on JSON data describing rack storages.

Dependencies

  • Requires connection to an external API that manages rack storage data.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for the API must be set in the node's credential configuration.

Troubleshooting

  • No results returned: Check if the filter parameters are too restrictive or incorrectly formatted, especially date/time strings which must follow ISO 8601 format.
  • Authentication errors: Ensure the API key or token is valid and has sufficient permissions.
  • Invalid parameter errors: Verify that numeric fields (e.g., company_id, height) are numbers and date filters are correctly formatted.
  • Network issues: Confirm that the base URL is reachable and there are no firewall or connectivity problems.

Links and References

Discussion