AvantGuard - HuduInstall

Overview

This node allows you to create a new IP address record in the Hudu system via the AvantGuard integration. It is useful for automating the management of IP addresses, such as adding new addresses to your inventory, associating them with assets or networks, and documenting their status and usage. Common scenarios include network provisioning, asset management, and maintaining up-to-date records for compliance or operational needs.

Example use cases:

• Automatically register a new IP address when provisioning a server.
• Assign an IP address to a specific asset or network.
• Document changes to IP allocations for audit trails.

Properties

Name	Type	Meaning
Address	String	The IP address to be created.
Status	String	The status of the IP address (e.g., unassigned, assigned, reserved, deprecated, dhcp, slaac).
Fqdn	String	The Fully Qualified Domain Name associated with the IP address.
Description	String	A brief description of the IP address.
Comments	String	Additional comments about the IP address.
Asset Id	Number	The identifier of the asset associated with this IP address.
Network Id	Number	The identifier of the network to which this IP address belongs.
Company Id	Number	The identifier of the company that owns this IP address.

All these properties are optional and can be provided as part of the "Additional Body Fields" collection.

Output

The node returns a JSON object representing the newly created IP address record. The structure typically includes all fields sent in the request, along with additional metadata generated by Hudu (such as unique identifiers, timestamps, etc.).

Example output:

{
  "id": 123,
  "address": "192.168.1.10",
  "status": "assigned",
  "fqdn": "server.example.com",
  "description": "Main office router",
  "comments": "Provisioned automatically",
  "asset_id": 456,
  "network_id": 789,
  "company_id": 101,
  "created_at": "2024-06-01T12:00:00Z",
  "updated_at": "2024-06-01T12:00:00Z"
}

Note: Actual output fields may vary depending on the Hudu API response.

Dependencies

• External Service: Requires access to a Hudu instance with the appropriate API enabled.
• API Key/Credentials: You must configure the avantguardHuduApi credential in n8n, including the base URL and authentication token.
• n8n Configuration: Ensure the node is properly installed and credentials are set up in your n8n environment.

Troubleshooting

• Missing Credentials:
  Error message: "No credentials found for 'avantguardHuduApi'."
  Resolution: Set up the required credentials in n8n under the name avantguardHuduApi.

• Invalid Input Data:
  Error message: "400 Bad Request" or similar from the API.
  Resolution: Check that all required fields are correctly filled and that values (like status) match allowed options.

• Connection Issues:
  Error message: "ENOTFOUND" or "ECONNREFUSED".
  Resolution: Verify the base URL in your credentials and ensure the Hudu API is reachable from your n8n instance.

• Permission Denied:
  Error message: "401 Unauthorized" or "403 Forbidden".
  Resolution: Make sure your API key has sufficient permissions to create IP addresses.

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• AvantGuard n8n OpenAPI Node