AvantGuard - HuduInstall

Overview

This n8n node allows you to retrieve a list of assets associated with a specific company from the Hudu API, as provided by AvantGuard. It is particularly useful for automating asset management workflows, such as syncing asset inventories, generating reports, or integrating asset data into other business processes.

Common scenarios:

• Fetching all assets belonging to a particular company for inventory tracking.
• Filtering assets based on archival status or paginating through large asset lists.
• Integrating asset data with other systems (e.g., CMDB, ticketing platforms).

Practical example:
You could use this node in an n8n workflow to automatically pull all assets for a given company and then process or export that data to another system.

Properties

Name	Type	Meaning
Company Id	Number	The identifier of the parent company whose assets you want to retrieve.
Additional Query Parameters	Collection	Optional parameters to refine your query: • Page (Number): Which page of results to fetch. • Archived (Boolean): If true, only archived assets are returned. • Page Size (Number): How many results per page.

Output

The node outputs a JSON object (or array of objects) representing the assets retrieved from the specified company. Each object typically contains details about an individual asset, such as its ID, name, type, and other relevant metadata as defined by the Hudu API.

Note: The exact structure of each asset object depends on the Hudu API schema.

Dependencies

• External Service: Requires access to the Hudu API.
• API Key/Credentials: You must configure the avantguardHuduApi credential in n8n, which should include the base URL (baseUrl) and authentication details for the Hudu instance.
• n8n Configuration: Ensure the credentials are set up in the n8n credential store.

Troubleshooting

Common issues:

• Invalid Company Id: If the provided Company Id does not exist, the API may return a 404 error or an empty result set.
• Authentication Errors: Missing or incorrect API credentials will result in authentication failures (401/403 errors).
• Pagination Issues: If the page number exceeds available pages, you may receive an empty array or an error.
• Network/Connectivity Problems: Ensure n8n can reach the Hudu API endpoint.

Error messages and resolutions:

• "401 Unauthorized": Check your API credentials in n8n.
• "404 Not Found": Verify the Company Id exists in Hudu.
• "400 Bad Request": Ensure all required fields are filled and query parameters are valid.

Links and References

• Hudu API Documentation
• n8n Documentation: Creating Workflows
• AvantGuard - Hudu Node GitHub