Skip to main content

Create Folder

Creates a new folder at the specified path in Dropbox.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

  • Client ID - The client identifier returned from the Connect node.
  • Dropbox Path - Path where the folder will be created (without leading slash).

How It Works​

The Create Folder node creates a new directory in your Dropbox account at the specified location. When executed, the node:

  1. Validates the required inputs (Client ID and Dropbox Path)
  2. Retrieves the access token using the provided Client ID
  3. Prepends "/" to the path as required by the Dropbox API
  4. Sends a create folder request to the Dropbox API
  5. Creates the new folder at the specified location

Path Format​

  • Paths should be provided without a leading slash
  • The node automatically adds the leading "/" for Dropbox API compatibility
  • Examples:
    • Input: documents/2024 → API uses: /documents/2024
    • Input: projects/new_project → API uses: /projects/new_project

Requirements​

  • A valid Dropbox connection (using the Connect node)
  • Write permissions for the parent folder
  • The parent folder must exist (e.g., to create documents/2024, the documents folder must exist)
  • The folder name must not already exist at that location

Error Handling​

The node will return specific errors in the following cases:

  • Empty or invalid Client ID
  • Empty Dropbox Path
  • Parent folder does not exist
  • Folder already exists at the specified path
  • Insufficient permissions
  • Invalid folder name (contains illegal characters)
  • Dropbox API errors

Usage Notes​

  • The folder is created immediately upon execution
  • You cannot create nested folders in a single call (parent folders must exist first)
  • Folder names are case-sensitive on some systems
  • Special characters in folder names may cause issues
  • The operation is idempotent - if the folder already exists, an error is returned

Example 1: Create a Simple Folder​

Create a new project folder:

Inputs:

  • Client ID: (from Connect node)
  • Dropbox Path: projects/website_redesign

Result: A new folder named website_redesign is created in the projects directory

Example 2: Create a Year-Based Archive Folder​

Create a folder for archiving documents by year:

Inputs:

  • Client ID: (from Connect node)
  • Dropbox Path: archive/2024

Result: A new folder 2024 is created in the archive directory

Example 3: Create Organization Structure​

Create a folder for a specific department:

Inputs:

  • Client ID: (from Connect node)
  • Dropbox Path: company/departments/marketing

Result: A marketing folder is created within company/departments/ (parent folders must already exist)

Common Use Cases​

  • Organizing files into category-based folders
  • Creating date-based folder structures for archiving
  • Setting up project directories for new initiatives
  • Automating folder creation for recurring workflows
  • Building hierarchical folder structures for data organization

Best Practices​

  • Verify parent folders exist before creating subfolders
  • Use consistent naming conventions across your automation
  • Include error handling for cases where folders already exist
  • Use descriptive folder names that clearly indicate their purpose
  • Consider creating folder structures in a specific order (parent to child)

Creating Nested Folder Structures​

To create multiple levels of folders, you need to create them one at a time:

Create Folder: company
  ↓
Create Folder: company/departments
  ↓
Create Folder: company/departments/marketing

Tips​

  • Use the Continue On Error property when creating folders that might already exist
  • Combine with ListFiles to check if a folder exists before creating it
  • Include timestamps in folder names for time-based organization (e.g., reports_2024-03-15)
  • Use the FileStat node to verify folder creation was successful
  • Consider using variables for dynamic folder names based on dates or user input

Avoiding Common Errors​

  • Parent folder doesn't exist: Create parent folders first before creating subfolders
  • Folder already exists: Use Continue On Error or check existence with FileStat first
  • Invalid characters: Avoid using special characters like :, *, ?, ", <, >, | in folder names
  • Empty path: Always provide a valid folder path