convertExcelToCSV Step

Use this feature to convert an Excel file into a CSV file and save the resulting CSV file to a specified location.

Last published at: September 28th, 2026

Description:

The Convert Excel to CSV workflow step converts a specified Excel file into CSV format.

The step supports:

  • Specifying the path of the source Excel file.
  • Specifying the path to save the CSV file.
  • Using workflow Variables or Globals to provide dynamic file paths.
  • Converting Excel-based data into a CSV file for subsequent workflow processing.
  • Passing the resulting CSV file to another workflow activity.
  • Returning a True or False result for subsequent workflow processing.

 

Inputs

  • inputFilePath - The inputFilePath property specifies the path of the Excel file that should be converted.
  • outputFilePath - The outputFilePath property specifies the path where the converted CSV file should be saved
 

 

Returns

  • True – The True return path can be connected to the next workflow activity after the conversion operation.
  • False – The False return path can be connected to an alternative workflow path or error-handling activity.
 

 

Usage:

The Convert Excel to CSV step is typically placed after an Excel file has been generated, received, uploaded, or otherwise made available to the workflow.

The source Excel file is supplied to the step, the destination CSV path is specified, and the resulting CSV file can then be used by subsequent workflow activities.

A typical workflow pattern is:

Get/Build Excel File Path → Convert Excel to CSV → Use CSV File

The resulting CSV file can then be used to:

  • Process tabular data.
  • Pass data to another workflow activity.
  • Prepare data for an integration.
  • Create a text-based data file.
  • Provide data to systems that consume CSV files.
  • Continue additional file processing.

 

 

Typical Workflow Suggestions:

Convert an Excel Report to CSV

Use the step after generating an Excel-based report when a CSV version is required.

Example:

Generate Excel Report
        ↓
Convert Excel to CSV
        ↓
Use CSV Report
For example:
C:\Reports\MonthlySales.xlsx
              ↓
     Convert Excel to CSV
              ↓
C:\Reports\MonthlySales.csv

 

Convert an Uploaded Excel File

Use Convert Excel to CSV after a workflow receives an Excel file.

Example:

Receive Excel File
        ↓
Convert Excel to CSV
        ↓
Process CSV Data
This can be useful when subsequent workflow processing requires a CSV representation of the uploaded data.

 

Prepare Data for an Integration

Convert an Excel file into CSV before passing the resulting file to a downstream integration.

Example:

Retrieve Excel File
        ↓
Convert Excel to CSV
        ↓
External Integration
The output CSV path can be supplied to the subsequent integration or file-processing activity.

 

Convert Excel Data for File-Based Processing

Use the step when a downstream workflow activity expects a CSV file.

Example:

Excel File
    ↓
Convert Excel to CSV
    ↓
CSV Processing
This provides a simple conversion stage between the Excel source and subsequent CSV-based processing.

 

Create a CSV Copy of a Workflow-Generated Excel File

A workflow can generate an Excel file and then create a CSV version.

Example:

Generate Excel
      ↓
Convert Excel to CSV
      ↓
Store / Send / Process CSV
This is useful when the same workflow needs to produce or process the data in both Excel and CSV formats.

 

Use Dynamic File Paths

Use workflow Variables or Globals when the source or destination file path depends on workflow data.

Example:

Get Process Information
        ↓
Build Excel File Path
        ↓
Convert Excel to CSV
        ↓
Build CSV File Path
For example, the workflow could construct paths based on a customer, process instance, reporting period, or other workflow data.

 

Convert Customer-Specific Excel Files

Use dynamically constructed paths to convert files associated with individual customers.

Example:

Get Customer Information
        ↓
Locate Customer Excel File
        ↓
Convert Excel to CSV
        ↓
Customer Data Processing
For example:
Input:
C:\CustomerData\Acme\Orders.xlsx

Output:
C:\CustomerData\Acme\Orders.csv

 

Convert a Periodic Excel Report

Use the step as part of a scheduled reporting workflow.

Example:

Collect Report Data
        ↓
Generate Excel Report
        ↓
Convert Excel to CSV
        ↓
Distribute CSV
The workflow can create a CSV representation of the report for subsequent processing or distribution.

 

Prepare a CSV File for Downstream Processing

Use ConvertExcelToCSV as an intermediate processing activity.

Example:

Retrieve Excel
      ↓
Convert Excel to CSV
      ↓
Read / Process CSV
      ↓
Continue Workflow
The destination CSV path is explicitly supplied to the conversion step.

 

Convert Excel Data Before an Archive Process

Use the step to create a CSV version of an Excel file before subsequent archival or distribution processing.

Example:

Excel Report
     ↓
Convert Excel to CSV
     ↓
Archive / Distribute
Later workflow activities can then handle the Excel file and generated CSV file according to the process design.

 

Generate Multiple CSV Files

Multiple Convert Excel to CSV steps can be used when a workflow needs to convert several Excel files.

Example:

Excel File 1 → Convert Excel to CSV → CSV File 1
Excel File 2 → Convert Excel to CSV → CSV File 2
Excel File 3 → Convert Excel to CSV → CSV File 3
Each step can specify its own source and destination paths.

 

Handle Conversion Failure

Use the False return path to handle cases where the conversion operation does not proceed successfully.

Example:

Convert Excel to CSV
       ├── True  → Continue Processing
       │
       └── False → Log / Notify / Handle Error
This provides a separate workflow path for alternate processing.

 

Example:

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

  • Create a new definition named “convertExcelToCSVDef” and open it in designer mode.
  • Drag a “convertExcelToCSV” step to the canvas.
  • Connect the dots between the “Start” and “convertExcelToCSV” steps, as shown above. 
  • Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
  • Click the “convertExcelToCSV” step to configure its “Required” properties. Provide a name for the step. Provide the source path to the Excel file (on the app server). Provide the target path (on the app server) where the CSV file will be stored. 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. Configure 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 and click the process step to view its properties. When the workflow reaches the Convert Excel to CSV step, verify that:
    • The source Excel file exists.
    • The source path is correct.
    • The destination CSV path is correctly configured.
    • The CSV file is created at the configured destination.
    • The workflow follows the appropriate True or False connection.

 

  • As configured, the process step should convert the Excel file to a CSV file at the specified path. 

 

Tips:

  • Provide a valid value for the Excel file Path.
  • Provide a valid destination path for the CSV file to be saved.
  • Both input properties are required by the step definition. 
  • Verify that the source Excel file exists before the step executes.
  • Verify that the destination location is available to the FlowWright execution environment.
  • Use Variables or Globals when file paths are generated dynamically.
  • Use meaningful file names for generated CSV files.
  • Keep environment-specific file locations configurable when the workflow is deployed across multiple environments.
  • Test the step using representative Excel files before deploying the workflow.
  • Test both the True and False workflow paths.
  • Consider connecting the False return path to appropriate error handling.
  • Verify that downstream activities reference the configured CSV output path.
  • When the same workflow processes files for different customers or process instances, construct the paths dynamically rather than hard-coding them.
  • Test files with the expected Excel structure and content.
  • Verify that the destination filename uses the intended .csv extension.
  • Make sure the FlowWright execution environment has appropriate access to the source and destination locations.
  • Test scenarios involving an invalid source file path.
  • Test scenarios involving an unavailable destination location.
  • Test file-system permissions for the FlowWright execution environment.
  • Test behavior when the destination CSV file already exists.
  • Do not assume details such as overwrite behavior, automatic directory creation, workbook selection, worksheet selection, encoding, or special Excel feature handling unless confirmed by the FlowWright implementation.

 

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

Before executing the imported definition, verify:

  • Path for the Excel file
  • Path for the CSV file to be saved
  • Workflow Variable references
  • Environment-specific file-system paths
  • Downstream True workflow path
  • Downstream False workflow path
  • Source-file availability
  • Destination location and access permissions

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.