AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node (Resource: Assets, Operation: Get Assets) retrieves a list of asset records from the Hudu API. This operation is useful for automating asset inventory management, synchronizing asset data with other systems, or filtering assets based on specific criteria such as company, name, serial number, or update time.

Common scenarios include:

• Fetching all assets for reporting or dashboard purposes.
• Filtering assets by company, ID, or custom search queries.
• Paginating through large sets of asset records.
• Integrating asset data into workflows for IT operations or compliance checks.

Example use cases:

• Retrieve all assets updated in the last week for audit.
• Find assets belonging to a specific company and export them to a spreadsheet.
• Search for assets by serial number to verify inventory status.

Properties

Name	Type	Meaning
Additional Query Parameters	collection	Optional query parameters to filter or paginate the returned assets.
└ Company Id	number	Filter assets by the parent company's ID.
└ Id	number	Filter assets by their unique ID.
└ Name	string	Filter assets by their name.
└ Primary Serial	string	Filter assets by their primary serial number.
└ Asset Layout Id	number	Filter assets by their associated asset layout's ID.
└ Page	number	Specify the page number of results to return (for pagination).
└ Archived	boolean	Set to true to display only archived assets.
└ Page Size	number	Limit the number of assets returned per page.
└ Slug	string	Filter assets by their URL slug.
└ Search	string	Filter assets using a search query.
└ Updated At	string	Filter assets updated within a range or at an exact time. Format: 'start_datetime,end_datetime' for range, 'exact_datetime' for exact match.

Output

The node outputs a list of asset objects in the json field. Each object represents an asset and contains fields as defined by the Hudu API, which typically include:

{
  "id": 123,
  "name": "Asset Name",
  "company_id": 456,
  "primary_serial": "SN123456",
  "asset_layout_id": 789,
  "archived": false,
  "slug": "asset-name",
  "updated_at": "2024-06-01T12:34:56Z",
  ...
}

• The actual structure may contain additional fields depending on your Hudu configuration.
• The output is always in JSON format; binary data is not produced by this operation.

Dependencies

• External Service: Requires access to a Hudu instance with API enabled.
• API Credentials: You must configure the avantguardHuduApi credential in n8n, including the base URL (baseUrl) and authentication details.
• n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common issues:

• Invalid credentials: If the API key or base URL is incorrect, you may receive authentication errors (e.g., 401 Unauthorized).
• Missing permissions: The API user must have permission to read assets.
• Incorrect query parameters: Supplying invalid values (e.g., non-existent IDs or malformed date ranges) may result in empty responses or API errors.
• Pagination confusion: Not specifying Page and Page Size may lead to incomplete data if there are many assets.

Error messages and resolutions:

• "401 Unauthorized": Check your API credentials and ensure they are correctly configured in n8n.
• "400 Bad Request": Review your query parameters for typos or invalid formats, especially for date/time fields.
• Empty result set: Adjust filters or remove restrictive parameters to broaden your search.

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• AvantGuard GitHub