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 interacts with the "Asset" resource of the Hudu API, specifically supporting the "Unarchive" operation among others. The Unarchive operation restores an archived asset back to an active state within the system.
Typical use cases include:
- Reactivating assets that were previously archived but are now needed again.
- Managing asset lifecycle by toggling archive status programmatically.
- Automating asset management workflows where assets may be archived/unarchived based on business rules or events.
For example, if a company had archived an old laptop asset but later decided to reuse it, this node can unarchive that asset by specifying its ID and associated company.
Properties
| Name | Meaning |
|---|---|
| Asset ID | The unique numeric identifier of the asset to operate on (required). |
| Company Name or ID | Select the company associated with the asset from a list or specify its ID. Required except when Asset ID is empty or zero. |
Output
The node outputs JSON data representing the result of the unarchive operation for each processed item. Each output item corresponds to one input item and includes details about the asset after the unarchive action.
The exact structure depends on the API response but typically includes fields such as asset ID, status, and other metadata confirming the asset is no longer archived.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the Hudu REST API.
- Needs the base URL of the Hudu instance configured in credentials.
- Uses internal helper methods to call the Hudu API endpoints related to assets.
- The node relies on dynamic loading of companies for the "Company Name or ID" property via an option loader method.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Asset ID will likely cause an error.
- Omitting the required Company selection when Asset ID is not specified or zero may cause validation errors.
- Network or authentication failures due to incorrect API key or base URL configuration.
Error messages:
"The resource "assets" is not known!"— This would occur if the resource parameter is incorrectly set; ensure "assets" is selected.- API errors returned from Hudu (e.g., 404 Not Found if asset does not exist) will be surfaced as node execution errors.
Resolutions:
- Verify the Asset ID exists and belongs to the selected company.
- Confirm API credentials and base URL are correct and have sufficient permissions.
- Use expressions carefully to dynamically provide IDs or company selections.
Links and References
- Hudu API Documentation (general reference for asset operations)
- n8n Expressions Documentation (for using expressions in properties)