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 belonging to a Company in the AvantGuard Hudu system. It is designed for scenarios where you need to programmatically mark an asset as archived, such as automating asset lifecycle management or integrating with other business processes that require assets to be deactivated or hidden from active use.
Example Use Cases:
- Automatically archiving assets when a company offboards.
- Integrating with ticketing systems to archive assets after incident resolution.
- Bulk archiving of assets based on compliance or audit requirements.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | The identifier of the requested Asset. This specifies which asset to archive. |
| Company Id | Number | The identifier of the parent Company. This determines under which company the asset resides. |
Output
The output will contain a json field reflecting the response from the Hudu API after attempting to archive the specified asset. The structure typically includes information about the asset and its new archived status. The exact fields depend on the API's response but may include asset details such as id, name, status, and timestamps.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Credentials: You must configure n8n credentials named
avantguardHuduApi, including at least thebaseUrlfor your Hudu instance. - n8n Configuration: Ensure the node has network access to the Hudu API endpoint.
Troubleshooting
Missing or Invalid Credentials:
Error: "401 Unauthorized" or similar authentication errors.
Resolution: Check that theavantguardHuduApicredentials are correctly set up in n8n and have the necessary permissions.Invalid Asset or Company ID:
Error: "404 Not Found" or "Asset not found".
Resolution: Verify that both the Asset Id and Company Id are correct and exist in the Hudu system.Insufficient Permissions:
Error: "403 Forbidden".
Resolution: Ensure the API user associated with your credentials has permission to archive assets.Network Issues:
Error: "ENOTFOUND", "ECONNREFUSED", or timeouts.
Resolution: Confirm that n8n can reach the Hudu API endpoint and there are no firewall or DNS issues.