AvantGuard - Hudu icon

AvantGuard - Hudu

AvantGuard - Hudu

Actions109

Overview

The AvantGuard - Hudu node for n8n allows users to interact with the Hudu API, specifically to retrieve a list of websites. The "Get Websites" operation fetches website records from Hudu, supporting various filters and pagination options. This is useful in scenarios where you need to automate reporting, synchronize website data with other systems, or build dashboards that reflect your Hudu-managed web assets.

Practical examples:

  • Fetch all websites managed in Hudu for inventory purposes.
  • Filter websites by name or slug to find specific entries.
  • Retrieve only recently updated websites for change tracking.
  • Paginate through large sets of website records.

Properties

Name Type Meaning
Additional Query Parameters collection Optional group of parameters to refine the query. Includes:
Page (number): Get current page of results.
Name (string): Filter websites by name.
Page Size (number): Number of results per page.
Slug (string): Filter by URL slug.
Search (string): Filter by search query.
Updated At (string): Filter by update time range or exact timestamp (ISO 8601).

Output

The node outputs a JSON array of website objects as returned by the Hudu API. Each object represents a website and includes fields such as ID, name, slug, and other metadata relevant to the website record.

Example output structure:

[
  {
    "id": 123,
    "name": "Example Website",
    "slug": "example-website",
    "updated_at": "2023-06-07T12:34:56Z",
    // ...other website fields
  },
  ...
]

Note: The actual fields depend on the Hudu API response.

Dependencies

  • External Service: Requires access to the Hudu API.
  • API Key/Credentials: Needs valid avantguardHuduApi credentials configured in n8n, including the base URL (baseUrl) for your Hudu instance.
  • n8n Configuration: Ensure the credentials are set up in n8n under the appropriate credential type.

Troubleshooting

Common issues:

  • Invalid Credentials: If the API key or base URL is incorrect, authentication errors will occur. Double-check your n8n credential configuration.
  • Missing Required Fields: If required query parameters are omitted or incorrectly formatted (e.g., invalid date format for "Updated At"), the API may return errors.
  • Pagination Issues: If "Page" or "Page Size" values are out of bounds, you may receive empty results or errors from the API.

Error messages and resolutions:

  • 401 Unauthorized: Check your API credentials and permissions.
  • 400 Bad Request: Review the query parameters, especially date formats and required fields.
  • 404 Not Found: Ensure the base URL is correct and the resource exists.

Links and References

Discussion