AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node for n8n allows you to interact with the Hudu API, specifically to retrieve a list of expirations. The "Get Expirations" operation under the "Expirations" resource fetches expiration records, which can be filtered and paginated using various query parameters. This is useful in scenarios where you need to monitor or report on expiring items such as domains, SSL certificates, warranties, assets, or articles within your Hudu environment.

Practical examples:

• Automatically generate reports of upcoming SSL certificate expirations.
• Filter and retrieve all asset warranties that are about to expire for a specific company.
• Integrate with notification workflows to alert teams about expiring resources.

Properties

Name	Type	Meaning
Additional Query Parameters	collection	Optional group of filters and pagination controls for the request. Contains the following options:
└─ Page	number	The current page of results to retrieve.
└─ Company Id	number	Filter expirations by company ID.
└─ Expiration Type	string	Filter expirations by type (e.g., undeclared, domain, ssl_certificate, warranty, asset_field, article_expiration).
└─ Resource Id	number	Filter logs by resource ID; must be used together with Resource Type.
└─ Resource Type	string	Filter logs by resource type (e.g., Asset, AssetPassword, Company, Article); must be used with Resource Id.
└─ Page Size	number	Number of results to return per page.

Output

The node outputs a JSON array of expiration objects. Each object typically contains details about an expiration, such as:

• The type of expiration (e.g., domain, SSL certificate)
• Associated resource information (ID, type)
• Company information
• Expiration date and status

Note: The exact structure of each expiration object depends on the Hudu API's response schema for the /expirations endpoint.

Dependencies

• External Service: Requires access to a Hudu instance with the API enabled.
• API Key/Credentials: Needs valid avantguardHuduApi credentials configured in n8n, including the base URL and authentication token.
• n8n Configuration: No special configuration beyond setting up the credentials.

Troubleshooting

Common Issues:

• Invalid Credentials: If the API key or base URL is incorrect, the node will fail to authenticate. Double-check your credential settings.
• Missing Required Filters: Some filters (like Resource Id and Resource Type) must be used together. Using one without the other may result in errors or empty responses.
• Pagination Issues: If no results are returned, ensure the correct page and page size are set.

Common Error Messages:

• "401 Unauthorized": Check your API credentials.
• "400 Bad Request": Likely due to missing required parameters or invalid filter combinations.
• "404 Not Found": The requested resource does not exist or the endpoint is incorrect.

Links and References

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