AvantGuard - Hudu icon

AvantGuard - Hudu

AvantGuard - Hudu
Join our community

Actions109

Overview

The AvantGuard - Hudu node for n8n allows users to interact with the Hudu API, specifically to retrieve a list of networks. The "Get Networks" operation fetches network records from Hudu, supporting various filters via query parameters. This is useful in scenarios where you need to automate inventory management, synchronize network data between systems, or generate reports based on network attributes.

Practical examples:

  • Fetch all networks belonging to a specific company.
  • Retrieve networks created or updated within a certain date range.
  • Filter networks by type, address, or location.

Properties

Name Type Meaning
Additional Query Parameters Collection Optional set of filters to refine the search for networks. Each field below can be added as needed:
└ Company Id Number Filter results to only include networks associated with a specific company ID.
└ Slug String Filter by the unique slug identifier of the network.
└ Name String Filter by the name of the network.
└ Network Type Number Filter by the type/category of the network.
└ Address String Filter by the network's address.
└ Location Id Number Filter by the location ID associated with the network.
└ Created At String Filter by creation date/time. Use 'start_datetime,end_datetime' for a range, or 'exact_datetime' for exact match.
└ Updated At String Filter by last update date/time. Use 'start_datetime,end_datetime' for a range, or 'exact_datetime' for exact match.

Output

  • The node outputs a JSON array of network objects.
  • Each object represents a network and includes fields such as id, name, slug, type, address, company_id, location_id, created_at, updated_at, etc., depending on the Hudu API response.
  • No binary output is produced by this operation.

Dependencies

  • External Service: Requires access to a Hudu instance with its API enabled.
  • API Key/Credentials: Needs valid credentials (avantguardHuduApi) configured in n8n, including the base URL and authentication token.
  • n8n Configuration: Ensure the credentials are set up under n8n’s credential manager.

Troubleshooting

Common Issues:

  • Invalid Credentials: If the API key or base URL is incorrect, the node will fail to connect. Double-check your credentials in n8n.
  • Missing Permissions: The API user must have permission to read network data in Hudu.
  • Incorrect Query Parameters: Supplying invalid values (e.g., non-existent company ID) may result in empty responses or errors.
  • Date Format Errors: For Created At and Updated At, ensure the date strings follow the required format (start_datetime,end_datetime or exact_datetime).

Error Messages:

  • 401 Unauthorized: Check your API credentials.
  • 400 Bad Request: Review your query parameters for typos or invalid values.
  • 404 Not Found: The resource does not exist; check IDs and slugs.

Links and References

Discussion