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 allows you to create a new folder within a system that organizes data or resources hierarchically. It is useful in scenarios where users need to programmatically manage folder structures, such as organizing documents, projects, or other entities into folders for better categorization and access control.
Practical examples include:
- Automatically creating project folders when a new project is initiated.
- Structuring client files by creating folders named after clients.
- Organizing assets or media files into categorized folders based on metadata.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to specify details about the folder being created. These include: |
| - Name | The name of the folder to be created. |
| - Icon | An icon representing the folder (e.g., emoji or icon code). |
| - Description | A textual description providing more information about the folder. |
| - Parent Folder Id | Numeric ID of an existing folder to set as the parent, enabling nested folder structure. |
| - Company Id | Numeric ID associating the folder with a specific company or organizational entity. |
Output
The node outputs JSON data representing the newly created folder. This typically includes the folder's unique identifier, its properties (name, icon, description), and any hierarchical relationships (such as parent folder ID). The output can be used downstream to reference the folder or confirm successful creation.
No binary data output is involved in this operation.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests.
- Depends on an external service endpoint (base URL provided via credentials) that manages folder creation.
- The node sends HTTP requests with JSON payloads to this service.
Troubleshooting
- Missing Required Fields: If the "Name" field is empty, the API may reject the request. Ensure the folder name is provided.
- Invalid Parent Folder ID: Providing a non-existent or unauthorized parent folder ID may cause errors. Verify the parent folder exists and is accessible.
- Authentication Errors: Failure to provide valid API credentials will result in authorization errors. Confirm credentials are correctly set up.
- API Endpoint Issues: Network problems or incorrect base URL configuration can cause request failures. Check connectivity and credential settings.
- Data Type Mismatches: Ensure numeric fields like "Parent Folder Id" and "Company Id" are numbers, not strings.
Links and References
- Refer to the external API documentation of the folder management service for detailed field descriptions and error codes.
- n8n documentation on setting up API credentials and HTTP request nodes for further customization.