AvantGuard - HuduInstall

Overview

The Update Network operation for the Networks resource allows you to update details of an existing network in your system. This node is useful when you need to programmatically modify network information, such as its name, address, type, or associated metadata, within automated workflows. Common scenarios include synchronizing network data between systems, updating network records after changes in infrastructure, or integrating with inventory and asset management tools.

Practical Example:
Suppose your organization updates the address or description of a network segment. You can use this node in an n8n workflow to automatically push those changes to your central database or third-party service.

---

Properties

Name	Type	Meaning
Id	Number	Network ID. The unique identifier of the network to be updated.
Additional Body Fields	Object	Optional collection of fields to update on the network. See below for available options.

Additional Body Fields Options:

• Id (Number): The unique identifier for the network.
• Name (String): The name of the network.
• Address (String): The network address, typically in CIDR notation.
• Network Type (Number): The type of network, represented as an integer.
• Slug (String): A slug representing the network.
• Company Id (Number): The identifier of the company that owns this network.
• Location Id (Number): The identifier of the location associated with this network.
• Description (String): A brief description of the network.
• Created At (String): The date and time when the network was created.
• Updated At (String): The date and time when the network was last updated.

---

Output

The node returns a json object containing the updated network's details as provided by the API response. The structure typically mirrors the fields sent in the request, including any updated values and possibly additional metadata from the server.

Example Output Structure:

{
  "id": 123,
  "name": "Office Network",
  "address": "192.168.1.0/24",
  "network_type": 1,
  "slug": "office-network",
  "company_id": 45,
  "location_id": 7,
  "description": "Main office LAN",
  "created_at": "2023-01-01T12:00:00Z",
  "updated_at": "2024-06-10T09:30:00Z"
}

Note: The actual output may vary depending on the API implementation.

---

Dependencies

• External Service: Requires access to the AvantGuard Hudu API.
• API Credentials: Needs valid credentials (avantguardHuduApi) configured in n8n, including the base URL and authentication token.
• n8n Configuration: Ensure the credentials are set up in the n8n credential store.

---

Troubleshooting

• Invalid Credentials:
  Error Message: "401 Unauthorized"
  Resolution: Check that your API key and base URL are correct in the n8n credentials.

• Missing Required Field:
  Error Message: "400 Bad Request" or similar
  Resolution: Ensure the "Id" property is provided and corresponds to an existing network.

• Network Not Found:
  Error Message: "404 Not Found"
  Resolution: Verify that the specified network ID exists in the target system.

• Field Validation Errors:
  Error Message: "422 Unprocessable Entity"
  Resolution: Check that all fields (e.g., address format, required fields) meet the API's validation rules.

---

Links and References

• n8n Documentation
• AvantGuard Hudu API Documentation (if available)
• CIDR Notation Reference

---