Hudu icon

Hudu

Interact with Hudu REST API

Overview

This node integration allows creating an Asset Password in the Hudu system via its REST API. It is useful for securely managing and storing passwords related to various assets within a company’s infrastructure or documentation system.

Typical use cases include:

  • Automating the creation of new asset passwords when onboarding new hardware or software.
  • Centralizing password management by programmatically adding credentials to the Hudu portal.
  • Associating passwords with specific companies, assets, or other related objects for easy retrieval and auditing.

For example, you could use this node to create a password entry for a server asset, including details like username, URL, and OTP secret, ensuring all relevant information is stored securely and accessible through the Hudu portal.

Properties

Name Meaning
Company Name or ID Select the company from a list or specify its ID where the asset password will be created.
Name The name identifier for the password entry.
Password The actual password string to store (input is masked).
Additional Fields A collection of optional fields to provide more context or metadata about the password:
- Description Notes or description related to the password.
- In Portal Boolean flag indicating if the password should be accessible in the user-facing portal.
- OTP Secret Secret key used for generating one-time passwords (OTP), if applicable (masked input).
- Password Folder ID Numeric ID of the folder where the password should be stored.
- Password Type Category or type of the password (masked input).
- Passwordable ID Numeric ID of the related object (e.g., a Website) that this password belongs to.
- Passwordable Type Type of the related object for the password. Options include Article, Asset, Company, User, Website, etc.
- URL URL associated with the password, if relevant.
- Username Username linked to the password.

Output

The node outputs JSON data representing the newly created asset password record as returned by the Hudu API. This typically includes all submitted fields along with any additional metadata assigned by the system, such as unique IDs or timestamps.

No binary data output is produced by this operation.

Dependencies

  • Requires a valid API key credential for authenticating with the Hudu REST API.
  • The base URL for the Hudu instance must be configured in the node credentials.
  • The node depends on the Hudu API being accessible and the authenticated user having permissions to create asset passwords.

Troubleshooting

  • Common issues:

    • Invalid or missing API key can cause authentication failures.
    • Providing an incorrect company ID or resource-related IDs may result in errors or failed creation.
    • Network connectivity problems to the Hudu API endpoint.
  • Error messages:

    • "The resource "asset_passwords" is not known!" indicates a misconfiguration in the resource parameter.
    • API errors returned from Hudu (e.g., validation errors) will be surfaced; ensure required fields are correctly filled.
  • Resolutions:

    • Verify API credentials and base URL configuration.
    • Double-check IDs and options selected correspond to existing entities in Hudu.
    • Enable continue-on-fail to handle partial failures gracefully during batch operations.

Links and References

Discussion