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 archive a specific Asset Password in the Hudu system by its ID. It is useful in scenarios where you need to programmatically mark an asset password as archived, for example, as part of an automated offboarding process or when cleaning up outdated credentials.
Practical Example:
Suppose your organization rotates passwords regularly and wants to ensure that old passwords are archived automatically after a new one is set. This node can be used in an n8n workflow to archive the previous password entry by providing its ID.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the requested Password to be archived. |
Output
The output will contain a JSON object reflecting the result of the archive operation. The structure typically includes confirmation of the action and may echo back the ID or status of the archived password. The exact fields depend on the Hudu API's response for this endpoint.
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 (baseUrl) for your Hudu instance. - n8n Configuration: Ensure the credentials are set up in n8n under the name
avantguardHuduApi.
Troubleshooting
- Invalid ID Error: If the provided ID does not correspond to an existing password, the node may return an error indicating "Not Found" or similar. 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.
- Connection Issues: Network problems or incorrect base URL can lead to connection timeouts or "Could not reach server" errors.