AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node for n8n allows you to interact with the Hudu API, specifically to retrieve asset passwords. The "Get Asset Passwords" operation fetches a list of asset passwords from your Hudu instance, supporting various filters and pagination options. This is useful in scenarios where you need to automate password management, audit access credentials, or integrate asset password data into other workflows.

Practical examples:

• Fetching all passwords associated with a specific company for compliance reporting.
• Retrieving recently updated passwords for synchronization with another system.
• Filtering passwords by name or slug for targeted automation tasks.

Properties

Name	Type	Meaning
Additional Query Parameters	collection	Optional query parameters to filter and control the results. Includes: • Name (string): Filter by password name. • Company Id (number): Filter by company ID. • Archived (boolean): Show only archived assets if true. • Page (number): Specify page number for paginated results. • Page Size (number): Number of results per page. • Slug (string): Filter by URL slug. • Search (string): Search query filter. • Updated At (string): Filter by update time; supports ISO 8601 date ranges or exact times.

Output

The node outputs a JSON array of asset password objects as returned by the Hudu API. Each object typically contains fields such as:

{
  "id": 123,
  "name": "Example Password",
  "company_id": 456,
  "archived": false,
  "slug": "example-password",
  "updated_at": "2023-06-07T12:34:56Z",
  // ...other password-related fields
}

• The structure may include additional fields depending on your Hudu configuration and API version.
• No binary output is produced by this operation.

Dependencies

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

Troubleshooting

Common Issues:

• Invalid Credentials: If the API key or base URL is incorrect, the node will fail to connect. Double-check your credentials in n8n.
• Missing Permissions: The API user must have permission to read asset passwords.
• Incorrect Query Parameters: Supplying invalid values (e.g., non-numeric company ID) may result in errors or empty results.
• Date Format Errors: The Updated At filter requires ISO 8601 format. Incorrect formatting can cause the API to reject the request.

Error Messages:

• "401 Unauthorized": Check your API credentials.
• "400 Bad Request": Review your query parameters for correct types and formats.
• "404 Not Found": The resource does not exist or the endpoint is incorrect.

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• ISO 8601 Date Format Reference