Hudu icon

Hudu

Interact with Hudu REST API

Overview

This node interacts with the Hudu REST API to retrieve multiple IP address records based on specified filters. It is designed to fetch a list of IP addresses that match given criteria such as exact IP address, asset ID, company, creation or update date ranges, FQDN, network ID, and status.

Common scenarios where this node is beneficial include:

  • Auditing or inventorying IP addresses assigned within an organization.
  • Filtering IP addresses by company or network for reporting or monitoring.
  • Retrieving recently updated or created IP addresses for synchronization with other systems.
  • Extracting IP addresses with specific statuses (e.g., assigned, reserved) for network management tasks.

Practical example:

  • A user wants to get all IP addresses assigned to a particular company that were updated in the last 7 days to check recent changes.
  • Another use case is fetching all unassigned IP addresses within a certain network to allocate them for new devices.

Properties

Name Meaning
Filters Collection of filters combined using AND logic to narrow down the IP addresses returned. Options include:
  Address Filter by exact IP address match (string).
  Asset ID Filter by asset ID (number).
  Company Name or ID Select from a list of companies or specify an ID via expression.
  Created At Filter IP addresses created at an exact date, within a date range, or preset ranges like "Last 7 Days", "This Month", etc.
  FQDN Filter by exact Fully Qualified Domain Name match (string).
  Network ID Filter by network ID (number).
  Status Filter by IP address status. Options: Assigned, Deprecated, DHCP, Reserved, SLAAC, Unassigned.
  Updated At Filter IP addresses updated at an exact date, within a date range, or preset ranges such as "Last 14 Days", "Today", "Yesterday", etc.

Output

The output is a JSON array where each item represents an IP address record matching the applied filters. Each JSON object contains the details of an IP address as returned by the Hudu API, including fields such as address, asset association, company, creation and update timestamps, FQDN, network information, and status.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.

Dependencies

  • Requires an active connection to the Hudu REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The base URL for the API is taken from the credentials configuration.
  • No additional external dependencies are indicated.

Troubleshooting

  • Common issues:

    • Incorrect or missing API key credential will cause authentication failures.
    • Using invalid filter values (e.g., non-existent company ID or malformed dates) may result in empty results or API errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "The resource \"ipAddresses\" is not known!" — This indicates an invalid resource parameter; ensure the resource is set correctly to "ipAddresses".
    • API errors related to authentication or permissions typically indicate issues with the API key or user rights.
    • Date filter misconfiguration might lead to no results; verify date formats and ranges.
  • Resolution tips:

    • Verify API key validity and permissions.
    • Double-check filter parameters for correctness.
    • Use debug mode to inspect input and output data for troubleshooting.

Links and References

Discussion