Hudu icon

Hudu

Interact with Hudu REST API

Overview

This node interacts with the Hudu REST API to retrieve multiple network records based on specified filters. It is designed to fetch a list of networks that match given criteria such as address, company association, creation or update dates, location, name, type, and slug.

Common scenarios where this node is beneficial include:

  • Automating inventory or asset management workflows by retrieving all networks related to a specific company or location.
  • Filtering networks updated within certain time frames for reporting or synchronization purposes.
  • Integrating network data into other systems or dashboards by extracting filtered network lists.

For example, you could use this node to get all networks created in the last month for a particular company, then process or analyze them downstream in your workflow.

Properties

Name Meaning
Filters A collection of optional filters to narrow down the networks retrieved:
- Address: Filter by network address (string).
- Company Name or ID: Select a company from a list or specify its ID.
- Created At: Filter networks created at an exact date, within a date range, or preset ranges like "Last 7 Days".
- Location ID: Filter by numeric location identifier.
- Name: Filter by network name (string).
- Network Type: Filter by numeric network type.
- Slug: Filter by network slug (string).
- Updated At: Filter networks updated at an exact date, within a date range, or preset ranges like "Last 14 Days".

Output

The output is a JSON array where each item represents a network object matching the applied filters. Each network object contains fields describing the network's properties as returned by the Hudu API.

  • The json field holds the network data.
  • The output items are paired with their input item index for traceability.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Hudu REST API.
  • Needs an API key credential configured in n8n for authentication.
  • The base URL for the API must be set in the node credentials.
  • Option loaders for companies are used to populate filter options dynamically.

Troubleshooting

  • No results returned: Check if the filters are too restrictive or incorrectly specified. For example, ensure date filters are valid and company IDs exist.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid filter values: Ensure numeric fields like Location ID and Network Type are numbers, and string filters do not contain unsupported characters.
  • API connectivity issues: Confirm network access to the Hudu API endpoint and correct base URL configuration.
  • Error messages referencing unknown resources: This indicates the resource parameter is incorrect; ensure "networks" is selected as the resource.

Links and References

Discussion