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
The "Post Folders" operation for the "Folders" resource in this custom n8n node allows users to create a new folder within an external system (likely Hudu, based on the node name). This operation is useful when you need to programmatically organize data or documents into folders, optionally specifying details such as the folder's name, icon, description, parent folder, and associated company. Typical use cases include automating the creation of project directories, structuring client documentation, or integrating with other systems that require dynamic folder management.
Example scenarios:
- Automatically creating a new client folder when onboarding a customer.
- Organizing files by project or department via workflow automation.
- Integrating with ticketing or CRM systems to maintain up-to-date folder structures.
Properties
| Name | Type | Meaning |
|---|---|---|
| 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). Used to nest this folder under another. |
| Company Id | Number | ID of the associated company (optional). |
All these properties are optional and can be provided as part of the "Additional Body Fields" collection.
Output
The output will be a JSON object representing the newly created folder. The exact structure depends on the API response from the external service, but typically it would include fields such as:
{
"id": 123,
"name": "Folder Name",
"icon": "folder-icon",
"description": "Description here",
"parent_folder_id": 0,
"company_id": 456,
// ...other metadata fields
}
No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Hudu API (or compatible service).
- API Credentials: You must configure credentials named
avantguardHuduApiin n8n, which should include at least abaseUrlproperty. - n8n Configuration: Ensure the node is installed and properly configured in your n8n instance.
Troubleshooting
Common Issues:
- Missing or Invalid Credentials: If the required API credentials are not set or incorrect, the node will fail to connect to the external service.
- Insufficient Permissions: The API user may lack permission to create folders, resulting in authorization errors.
- Invalid Input Data: Providing invalid types (e.g., string instead of number for IDs) or missing required fields (if enforced by the API) may cause errors.
Common Error Messages:
"401 Unauthorized": Check your API credentials and permissions."400 Bad Request": Review the input fields for correct types and required values."404 Not Found": The specified parent folder or company ID does not exist.
How to resolve:
- Double-check credential configuration in n8n.
- Verify all input fields for correct data types and valid references.
- Consult the external service's API documentation for field requirements.
Links and References
- n8n Documentation
- Hudu API Documentation (if applicable)
- AvantGuard n8n Nodes GitHub (if available)