AvantGuard - HuduInstall

Overview

This node allows you to update an existing Asset Layout in the Hudu system by specifying its ID and providing updated fields. It is useful for automating the management of asset layouts, such as changing their properties, toggling features (like including passwords or files), or updating display settings. Common scenarios include synchronizing asset layout configurations across environments, bulk-updating layouts based on external data, or integrating with other systems that manage asset metadata.

Example use cases:

• Automatically update the name and color of an asset layout when a related event occurs.
• Enable or disable specific features (e.g., comments, photos) for certain asset layouts via workflow automation.
• Batch-update icon or password type settings for multiple layouts.

Properties

Name	Type	Meaning
Id	Number	ID of the Asset Layout to be updated.
Additional Body Fields	Collection	Optional fields to update in the Asset Layout. Includes:
└ Fields	JSON	An array of field names for the Asset Layout.
└ Active	Boolean	If true, the Asset Layout is active.
└ Icon Color	String	Hex code for the icon color.
└ Color	String	Hex code for the background color.
└ Icon	String	Icon class name.
└ Name	String	Name of the Asset Layout.
└ Include Passwords	Boolean	If true, include passwords in the Asset Layout.
└ Include Photos	Boolean	If true, include photos in the Asset Layout.
└ Include Comments	Boolean	If true, include comments in the Asset Layout.
└ Include Files	Boolean	If true, include files in the Asset Layout.
└ Password Types	String	List of password types, separated with new line characters.

Output

The node returns the updated Asset Layout object in the json output field. The structure typically mirrors the Asset Layout resource from Hudu, containing all relevant fields after the update (such as id, name, color, icon, active status, included features, etc.).

Example output:

{
  "id": 123,
  "name": "Updated Layout",
  "active": true,
  "icon_color": "#FF0000",
  "color": "#00FF00",
  "icon": "fa-solid fa-key",
  "fields": ["field1", "field2"],
  "include_passwords": true,
  "include_photos": false,
  "include_comments": true,
  "include_files": true,
  "password_types": "type1\ntype2"
}

Note: Actual output fields depend on the Hudu API response.

Dependencies

• External Service: Requires access to a Hudu instance with API enabled.
• API Credentials: Needs valid credentials (avantguardHuduApi) configured in n8n, including the base URL and API key.
• n8n Configuration: No special environment variables beyond standard credential setup.

Troubleshooting

Common Issues:

• Invalid ID: If the provided Asset Layout ID does not exist, the API will likely return a "Not Found" error.
• Missing Required Fields: Omitting the required "Id" property will result in validation errors.
• Authentication Errors: Incorrect or missing API credentials will cause authentication failures.
• Malformed JSON: Providing invalid JSON in the "Fields" property can lead to parsing errors.

Error Messages & Resolutions:

• "404 Not Found": Check that the Asset Layout ID exists in your Hudu instance.
• "401 Unauthorized": Verify your API credentials and permissions.
• "400 Bad Request": Ensure all required fields are present and correctly formatted, especially any JSON input.

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• AvantGuard n8n OpenAPI Node