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 move an asset to a new layout within a specific company in the Hudu system via the AvantGuard integration. It is useful for automating asset management tasks, such as reorganizing assets when company structures change or when updating asset categorization. For example, you might use this node to bulk-move assets to a new layout after a company merger or restructuring.
Properties
| Name | Type | Meaning |
|---|---|---|
| Company Id | Number | ID of the parent company whose asset is being moved. Required to specify which company's asset should be updated. |
| Id | Number | ID of the asset to move. This identifies the specific asset that will be relocated to a new layout. |
| Asset Layout Id | Number | ID of the new asset layout. The asset will be moved to this layout within the specified company. |
Output
The output will contain a JSON object representing the result of the asset move operation. Typically, this includes details about the updated asset, such as its new layout and confirmation of the move. The exact structure depends on the Hudu API response, but you can expect fields like asset id, company id, and asset layout id.
Dependencies
- External Service: Requires access to the Hudu API.
- 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
- Missing Credentials: If credentials are not provided or incorrect, the node will fail with an authentication error. Make sure the
avantguardHuduApicredential is correctly configured. - Invalid IDs: Providing non-existent or incorrect
Company Id,Id, orAsset Layout Idwill result in errors from the Hudu API, such as "Not Found" or "Invalid ID". - Permission Issues: The API key used must have sufficient permissions to move assets; otherwise, you may receive authorization errors.