Actions100
- Activity Logs Actions
- Articles Actions
- 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
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation updates an existing folder by its ID. It allows modifying various folder attributes such as the folder's name, icon, description, parent folder, and associated company. This is useful in scenarios where folder metadata needs to be maintained or reorganized dynamically, for example, updating project folders in a document management system or adjusting organizational structures in a CRM.
Practical examples:
- Renaming a folder to reflect a new project phase.
- Changing the icon of a folder to visually distinguish it.
- Moving a folder under a different parent folder to reorganize hierarchy.
- Adding or updating a description to provide more context about the folder.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the folder to update (required). |
| Additional Body Fields | Optional fields to update on the folder: |
| - Name | New name for the folder (string). |
| - Icon | Icon representing the folder (string). |
| - Description | Textual description of the folder (string). |
| - Parent Folder Id | Numeric ID of the new parent folder to move this folder under (optional). |
| - Company Id | Numeric ID of the company associated with the folder (optional). |
Output
The node outputs JSON data representing the updated folder object after the operation completes successfully. This typically includes the folder's current state with all updated properties reflected.
If the API supports binary data output (not indicated here), it would represent any file or media content related to the folder, but this operation focuses on metadata updates only.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing folders.
- The base URL for the API must be configured in the node credentials.
- The node depends on the external AvantGuard API service (as inferred from bundled code naming) to perform folder updates.
Troubleshooting
- Invalid Folder ID: If the provided folder ID does not exist, the API will likely return a "not found" error. Verify the ID before running the node.
- Missing Required Fields: The
Idproperty is mandatory; omitting it will cause the node to fail. - Permission Issues: Insufficient permissions or invalid API credentials can cause authorization errors. Ensure the API key has rights to update folders.
- Invalid Field Values: Providing incorrect types (e.g., string instead of number for IDs) may result in validation errors.
- API Connectivity: Network issues or incorrect base URL configuration can prevent successful API calls.
Links and References
- Refer to the external API documentation for detailed information on folder resource endpoints and field constraints.
- n8n documentation on how to configure API credentials and use collection-type input properties.