Description:

The Check if Folder Exists step enables a FlowWright workflow to verify whether a specified folder exists on a local drive, a mapped network drive, or an accessible shared location.

This step is commonly used before performing operations such as creating files, copying documents, importing data, exporting reports, or processing file-based integrations. By validating the existence of a folder before executing these operations, workflows can avoid runtime errors and provide meaningful handling when expected directories are unavailable.

The step evaluates the configured folder path and determines whether the directory exists. Based on the result, the workflow follows either the True or False execution path.

Typical uses include:

• Verifying import directories
• Checking export locations
• Confirming archive folders
• Validating document storage paths
• Verifying shared network locations
• Preparing file processing workflows
• Preventing file system errors

This step is particularly useful in automated workflows that depend on external file storage or shared network resources.

Usage:

The Check if Folder Exists step is typically used immediately before any workflow activity that depends on an existing directory.

During execution:

1. Read the configured folder path.
2. Verify whether the folder exists.
3. If the folder exists, continue through the True path.
4. If the folder does not exist, continue through the False path and perform appropriate handling.

A typical workflow might look like this:

Typical workflow scenarios include:

• Verifying document repository locations
• Checking inbound integration folders
• Confirming backup directories
• Validating export destinations
• Verifying shared network folders
• Confirming archive locations before moving files
• Preparing automated document processing workflows

Example:

Let’s build and execute the “folderExistDef” example.          

• Create a new process definition named “folderExistDef” and open it in Designer mode. 
• Drag a “folderExist and placeHolders” step to the canvas. 
• Connect the dots between the “Start” step and other steps, as shown above. Click the connection link to configure the “TRUE and FALSE” workflow paths. 
• Click the "folderExist" step to configure its "Required" properties. Provide a name for the step and the folder path on the application server. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. The step verifies the folder's existence and configures the “TRUE or FALSE” path. In this case, the workflow takes the “TRUE” path because the folder exists. 

Tips:

• Store folder paths in workflow variables or global variables when the location changes between environments.
• Validate folder existence before copying, moving, reading, or writing files.
• Route the False path to notification, retry, or folder creation logic where appropriate.
• Use UNC paths for shared network folders when workflows execute across multiple servers.
• Ensure the FlowWright service account has permission to access the specified folder.
• Use descriptive variable names when folder paths are dynamically generated.
• Combine this step with Create Folder, Copy File, Move File, Delete File, Read File, Write File, or Loop Each File steps to build reliable file-processing workflows.

Notes:

• The folder path is required before the step can execute.
• The step verifies only the existence of the specified folder; it does not create or modify directories.
• Accessibility depends on the permissions of the account under which the FlowWright workflow is executing.
• A False return may indicate that the folder does not exist or that it cannot be accessed because of permissions or unavailable network resources.
• Both the True and False return paths should be implemented to provide complete workflow handling.
• Execution details and folder validation results are recorded in the FlowWright workflow execution log.

Check if Folder Exists vs. Create Folder:

Both workflow steps work with file system directories, but they serve different purposes.

As a general guideline:

• Use Check if Folder Exists when a workflow must verify that a directory is available before performing file operations.
• Use Create Folder when a workflow needs to create a directory that does not already exist.

Definition Sample:

You may download the sample workflow definition from the link provided and import it into your FlowWright environment.

Note: Verify and complete any missing configuration after importing the sample, including:

• Folder path
• Workflow variables or global variables (if used)
• Success and failure workflow branches
• Notification or recovery logic
• Appropriate file system permissions

After verifying the configuration, save and publish the workflow before execution.

Click here to download the sample file.