AvantGuard - Hudu icon

AvantGuard - Hudu

AvantGuard - Hudu

Actions109

Overview

This node allows you to update (PUT) the details of a specific website in your AvantGuard Hudu system by its ID. It is useful for automating the management of website records, such as updating their name, associating them with a company, or toggling monitoring features like DNS, SSL, and WHOIS checks.

Common scenarios:

  • Automatically pausing or resuming monitoring for a website.
  • Updating website metadata (name, notes) from another workflow.
  • Associating websites with different companies based on business logic.

Practical example:
If you have a workflow that detects a website's downtime, you could use this node to automatically pause monitoring for that site and add a note explaining why.

Properties

Name Type Meaning
Id Number ID of the requested website. This identifies which website record will be updated.
Additional Body Fields Object Optional fields to update additional website properties. See below for sub-fields.

Additional Body Fields (Collection):

Name Type Meaning
Company Id Number Used to associate the website with a specific company.
Name String The name or URL of the website.
Notes String Add additional notes to a website.
Paused Boolean When true, website monitoring is paused.
Disable Dns Boolean When true, DNS monitoring is paused.
Disable Ssl Boolean When true, SSL certificate monitoring is paused.
Disable Whois Boolean When true, WHOIS monitoring is paused.

Output

The node returns the JSON response from the AvantGuard Hudu API after updating the website. The structure of the output json field will reflect the updated website object as returned by the API, typically including fields such as the website's id, name, associated company, status flags (paused, disable_dns, etc.), and any notes.

Example output structure:

{
  "id": 123,
  "company_id": 456,
  "name": "example.com",
  "notes": "Monitoring paused due to maintenance.",
  "paused": true,
  "disable_dns": false,
  "disable_ssl": false,
  "disable_whois": true,
  ...
}

Dependencies

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

Troubleshooting

  • Missing or Invalid Credentials:
    Error message: "401 Unauthorized" or "Invalid API key."
    Resolution: Check that the correct API credentials are provided and have sufficient permissions.

  • Website Not Found:
    Error message: "404 Not Found"
    Resolution: Verify that the "Id" property matches an existing website in your Hudu instance.

  • Validation Errors:
    Error message: "400 Bad Request"
    Resolution: Ensure all required fields are filled and data types match expectations (e.g., numbers for IDs, booleans for toggles).

  • Connection Issues:
    Error message: "ENOTFOUND" or "ECONNREFUSED"
    Resolution: Confirm the base URL is correct and the Hudu server is reachable from your n8n instance.

Links and References

Discussion