Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
This node allows you to update (replace) an existing Asset Password in the Hudu system by specifying its ID and providing new password data. It is useful for automating the management of sensitive credentials stored as asset passwords, ensuring they remain up-to-date and secure.
Common scenarios:
- Automatically updating passwords when rotating credentials.
- Integrating with other systems that manage or generate passwords.
- Ensuring compliance by programmatically updating asset passwords after audits.
Example:
You have a workflow that generates new strong passwords for your assets every 90 days. This node can be used to push those new passwords into Hudu, replacing the old ones.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the requested Password. Specifies which asset password record to update. |
| Additional Body Fields | Collection | Optional fields to include in the request body. |
| └ Asset Password | JSON | The new asset password data to set. Should be provided as a valid JSON object. |
Output
The output will contain the updated asset password record in JSON format, reflecting the changes made. The structure typically includes all fields of the asset password as returned by the Hudu API after the update.
Dependencies
- External Service: Requires access to a Hudu instance with API enabled.
- API Key/Credentials: Needs valid
avantguardHuduApicredentials configured in n8n, including the base URL and authentication token. - n8n Configuration: Ensure the credentials are set up under "avantguardHuduApi" in your n8n instance.
Troubleshooting
- Invalid ID Error: If the specified ID does not exist, the node may return a "Not Found" or similar error. Double-check the ID value.
- Authentication Errors: If credentials are missing or incorrect, you may see errors like "401 Unauthorized." Ensure your API key and base URL are correct.
- Malformed JSON: If the "Asset Password" field contains invalid JSON, the node will fail. Always provide properly formatted JSON.