AvantGuard - HuduInstall

Overview

The Post Asset Layouts operation for the Asset Layouts resource in this custom n8n node allows users to create new asset layouts within the Hudu system via the AvantGuard integration. This is useful for organizations that need to programmatically define or update how assets are structured, including their fields, icons, colors, and which types of data (like passwords, photos, comments, files) should be included.

Common scenarios:

• Automating the setup of standardized asset layouts across multiple environments.
• Integrating asset layout creation into onboarding workflows.
• Bulk-creating or updating asset layouts based on external configuration files.

Practical example:
A company wants to ensure all client records have a consistent structure with specific fields, icons, and color coding. Using this node, they can automate the creation of these layouts as part of their provisioning process.

---

Properties

Name	Type	Meaning
Name	String	Name of the Asset Layout.
Icon	String	Icon class name representing the layout visually.
Color	String	Hex code for the background color of the layout.
Icon Color	String	Hex code for the icon color.
Include Passwords	Boolean	If true, passwords will be included in the Asset Layout.
Include Photos	Boolean	If true, photos will be included in the Asset Layout.
Include Comments	Boolean	If true, comments will be included in the Asset Layout.
Include Files	Boolean	If true, files will be included in the Asset Layout.
Password Types	String	List of password types to include, separated by new line characters.
Fields	JSON	An array of field definitions for the Asset Layout.

---

Output

The node returns the response from the Hudu API after creating the asset layout. The output json field typically contains:

• Details of the newly created asset layout, such as its ID, name, icon, color, included sections (passwords, photos, etc.), password types, and the array of fields.
• Any additional metadata returned by the API.

Example output structure:

{
  "id": 123,
  "name": "Server Layout",
  "icon": "server",
  "color": "#FF0000",
  "icon_color": "#FFFFFF",
  "include_passwords": true,
  "include_photos": true,
  "include_comments": false,
  "include_files": true,
  "password_types": "Admin\nUser",
  "fields": [
    { "label": "Hostname", "type": "string" },
    { "label": "IP Address", "type": "string" }
  ],
  // ...other metadata
}

Note: The actual structure may vary depending on the Hudu API's response.

---

Dependencies

• External Service: Requires access to a Hudu instance with API enabled.
• API Key: Needs valid credentials (avantguardHuduApi) configured in n8n.
• Environment Variable: The base URL for the Hudu API must be set in the credentials as baseUrl.

---

Troubleshooting

Common issues:

• Invalid Credentials: If the API key or base URL is incorrect, authentication errors will occur.
• Missing Required Fields: Omitting required fields like "Name" or providing invalid JSON in "Fields" may result in validation errors from the API.
• Malformed JSON: Supplying improperly formatted JSON in the "Fields" property will cause parsing errors.

Common error messages:

• "401 Unauthorized": Check your API key and base URL.
• "400 Bad Request": Review the input properties, especially the "Fields" JSON.
• "500 Internal Server Error": There may be an issue with the Hudu server; try again later or contact support.

---

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• AvantGuard GitHub