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 an existing folder in the Hudu system by specifying its ID and providing new values for its properties. It is useful in scenarios where you need to programmatically modify folder details, such as renaming a folder, changing its icon, updating its description, or moving it under a different parent folder. For example, you might use this node in an automation workflow to reorganize folders based on certain triggers or to keep folder metadata up-to-date.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | ID of the folder to update. |
| Additional Body Fields | Object | Optional collection of fields to update: |
| - Name | String | Name of the folder. |
| - Icon | String | Icon for the folder. |
| - Description | String | Description of the folder. |
| - Parent Folder Id | Number | ID of the parent folder (optional). |
| - Company Id | Number | ID of the associated company (optional). |
Output
The output will be a JSON object representing the updated folder. The structure typically includes the folder's properties after the update, such as its ID, name, icon, description, parent folder ID, and company ID. The exact fields depend on the API response from Hudu.
Dependencies
- External Service: Requires access to the Hudu API.
- API Key/Credentials: Needs valid
avantguardHuduApicredentials configured in n8n, including the base URL and authentication token. - n8n Configuration: Ensure that the credentials are set up in n8n under the name
avantguardHuduApi.
Troubleshooting
- Invalid Folder ID: If the provided folder ID does not exist, the node may return an error indicating that the folder was not found. Double-check the ID value.
- Missing Credentials: If credentials are not properly configured, you may see authentication errors. Ensure the
avantguardHuduApicredential is set up with the correct base URL and API key. - Insufficient Permissions: If the API key lacks permission to update folders, the request will fail. Verify the permissions associated with your API key.
- Validation Errors: If required fields are missing or invalid data types are provided (e.g., non-numeric ID), the API may return validation errors. Check input values carefully.