AvantGuard - Hudu icon

AvantGuard - Hudu

AvantGuard - Hudu

Actions109

Overview

This node updates an existing IP address record in the Hudu system via the AvantGuard integration. It is designed for scenarios where you need to modify details of a specific IP address, such as changing its status, updating its associated asset or network, or adding descriptive information. This is useful in IT asset management, network administration, or automated documentation workflows where keeping IP address records up-to-date is essential.

Example use cases:

  • Automatically update the status of an IP address when a device is decommissioned.
  • Change the description or comments on an IP address after a network audit.
  • Associate an IP address with a different asset or network as part of infrastructure changes.

Properties

Name Type Meaning
Id Number The unique identifier of the IP address to update.
Additional Body Fields Collection Optional fields to update additional properties of the IP address. Includes:
— Address String The new IP address value.
— 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 Identifier of the asset associated with this IP address.
— Network Id Number Identifier of the network to which this IP address belongs.
— Company Id Number Identifier of the company that owns this IP address.

Output

The node returns the updated IP address object as JSON. The structure typically includes all the fields of the IP address after the update, such as id, address, status, fqdn, description, comments, asset_id, network_id, and company_id.

Example output:

{
  "id": 123,
  "address": "192.168.1.10",
  "status": "assigned",
  "fqdn": "server.example.com",
  "description": "Main server IP",
  "comments": "Updated after migration",
  "asset_id": 456,
  "network_id": 789,
  "company_id": 101
}

Note: The actual output fields may vary depending on the API response.

Dependencies

  • External Service: Requires access to a Hudu instance with the AvantGuard API enabled.
  • API Credentials: Needs an n8n credential named avantguardHuduApi with at least a baseUrl property configured.
  • n8n Configuration: Ensure the credentials are set up in n8n under the appropriate name.

Troubleshooting

  • Missing or Invalid Credentials:
    Error message: "401 Unauthorized" or "Invalid credentials"
    Resolution: Check that the avantguardHuduApi credential is correctly configured with the right base URL and API key.

  • IP Address Not Found:
    Error message: "404 Not Found"
    Resolution: Verify that the provided Id matches an existing IP address in Hudu.

  • Validation Errors:
    Error message: "400 Bad Request"
    Resolution: Ensure all required fields are provided and values (such as status) conform to allowed options.

  • Network/Connection Issues:
    Error message: "ENOTFOUND", "ECONNREFUSED", etc.
    Resolution: Confirm network connectivity to the Hudu API endpoint.

Links and References

Discussion