Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node operation updates an existing Asset Password in the Hudu system via its REST API. It allows users to modify various attributes of a stored password related to assets, such as changing the password string, updating descriptive information, associating it with different companies or folders, and managing access settings.
Common scenarios where this node is beneficial include:
- Rotating or changing passwords for assets securely without manual intervention.
- Updating metadata or organizational details about asset passwords to keep records current.
- Managing access control by toggling whether a password is visible in a user portal.
- Associating passwords with different related objects like websites, users, or companies.
Practical example: An IT administrator automates the update of asset passwords after a security audit, ensuring all passwords are changed and descriptions updated accordingly in the central Hudu repository.
Properties
| Name | Meaning |
|---|---|
| Asset Password ID | The unique numeric identifier of the asset password to update. This is required to specify which password record will be modified. |
| Update Fields | A collection of fields that can be updated on the asset password. These include: |
| - Company Name or ID | Select from a list of companies or specify a company ID to associate the password with a particular company. |
| - Description | Text notes or description related to the password. |
| - In Portal | Boolean flag indicating if the password should be accessible/viewable in the portal. |
| - Name | The name or label of the password entry. |
| - OTP Secret | Secret key used for one-time password (OTP) generation, if applicable. Stored securely as a password-type field. |
| - Password | The actual password string itself, stored securely. |
| - Password Folder ID | Numeric ID of the folder where the password is stored, allowing organization into folders. |
| - Password Type | Category or type of the password, stored securely. |
| - Passwordable ID | Numeric ID of the related object (e.g., a Website or Asset) that this password belongs to. |
| - Passwordable Type | The type/category of the related object for the password. Options include Article, Asset, Company, User, Website, etc. |
| - URL | URL associated with the password, if relevant (e.g., login page). |
| - Username | Username linked to the password, if applicable. |
Output
The node outputs a JSON array containing the updated asset password data returned from the Hudu API after the update operation. Each item corresponds to one input item processed and includes the updated fields reflecting the changes made.
No binary data output is involved in this operation.
Dependencies
- Requires a valid API key credential for authenticating with the Hudu REST API.
- The base URL for the Hudu API must be configured in the node credentials.
- The node depends on the Hudu API being accessible and the specified Asset Password ID existing in the system.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Asset Password ID will result in errors.
- Missing required authentication credentials or incorrect API keys will cause authorization failures.
- Attempting to update fields with invalid data types or unsupported values may lead to API validation errors.
Error Messages:
"The resource "asset_passwords" is not known!"— indicates the resource parameter was incorrectly set; ensure "asset_passwords" is selected.- API error responses typically include messages about missing permissions, invalid IDs, or malformed requests. Review the error message and verify input parameters.
Resolution Tips:
- Double-check the Asset Password ID exists before attempting an update.
- Ensure all required credentials and API configurations are correctly set up.
- Validate input fields conform to expected types and constraints.
- Use the node's "Continue On Fail" option to handle individual item errors gracefully during batch processing.
Links and References
- Hudu API Documentation — Official API docs for reference on asset password endpoints and payload structure.
- n8n Expressions Documentation — For using expressions to dynamically set property values.
- Hudu Portal User Guide — Information on portal visibility and password management features.