Description:
This step encrypts files and stores the encrypted output.
The Encrypt and Store Files workflow step reads one or more source files, encrypts their contents using the configured encryption mechanism, and writes the encrypted files to the specified output locations.
The step supports encrypting a single file by specifying input and output file paths, or processing multiple files in a single operation using a configurable file-mapping list.
This step provides an efficient way to automate secure document handling, confidential file exchange, regulatory compliance, archival protection, and enterprise document security within FlowWright workflows.
The step supports:
- Single file encryption
- Multiple file encryption
- Batch file processing
- Configurable input and output locations
- File mapping support
- Integration with FlowWright workflow automation
This step can be used for:
- Secure document storage
- Confidential document exchange
- Compliance workflows
- Secure archival
- Data protection
- File processing automation
- Business process automation
Inputs
- Input File Path – Specify the full path of the source file to encrypt.
- Encrypted File Path – Specify the full path where the encrypted file will be written.
- File Mappings – Configure one or more input/output file mappings for batch encryption. Each mapping associates a source file with its encrypted output file.
Note: You can configure either a single Input File Path and Encrypted File Path pair or use File Mappings to encrypt multiple files during a single workflow step.
Returns
- True – The file or files were successfully encrypted and stored.
- False – One or more files could not be encrypted or written to the specified output location.
Usage:
The Encrypt and Store Files step is typically placed after document generation, report creation, export operations, or file preparation activities where documents must be secured before storage or transmission.
The workflow reads the source file or files, encrypts their contents, writes the encrypted output to the configured destination, and makes the encrypted files available for subsequent workflow steps.
A typical workflow might look like this:

Once the files have been encrypted, later workflow steps can:
- Upload files to secure repositories
- Send encrypted email attachments
- Archive protected documents
- Transfer files to external systems
- Maintain compliance records
- Continue workflow execution
The source files must already exist and be accessible before this step is executed.
Example:
Let’s build and execute the “encryptFilesDef” example.
- Create a new process definition named “encryptFilesDef” and open it in Designer mode.
- Drag a “encryptFiles” step to the canvas.
- Connect the dots between the “Start” and “encryptFiles” steps, as shown above.
- Click the "encryptFiles" step to configure its "Required" properties. Provide a name for the step. Provide a variable or global reference to store the process definition GUID. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.

- Click the "encryptFiles" step to configure its "Optional" properties. Click the button to configure multiple file mappings. A pop-up window will appear for configuration. Click the Add Row (+) button to insert an empty row. Enter the input and output file paths. Click the Save button. You may add multiple file paths for encryption using the Add Row button.

- 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 in the images below. Configure the “Logging” using the following properties.

- Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Encrypt and Store Files step, FlowWright reads the configured source file or file mappings, encrypts each file, and writes the encrypted output to the specified destination. If the operation completes successfully, the workflow follows the True return path. If a source file cannot be located, the encryption process fails, the encrypted output cannot be created, or file permissions prevent access, the workflow follows the False return path. Click the process step to view its properties. The step should successfully encrypt the configured files, generate the encrypted output files, and return True upon completion.

Tips:
- Verify that the source files exist before executing the workflow.
- Ensure the FlowWright server has permission to read the source files and write the encrypted output files.
- Use File Mappings when encrypting multiple files within a single workflow execution.
- Store encrypted files in secure storage locations with appropriate access controls.
- Encrypt documents before transferring them across external networks or storing them in shared repositories.
- Validate the encrypted output during testing to ensure downstream systems can successfully decrypt the files.
- Use the True and False return paths to implement appropriate success and exception handling.
- Combine this step with Generate Document, Convert Word to Text, PDF to HTML, Decrypt and Store Files, Archive Document, or Upload Document workflow steps to automate secure document lifecycle management.
Notes:
- The source files must be accessible to the FlowWright server.
- Either a single input/output file pair or multiple file mappings may be configured.
- The encrypted output files are written to the specified destination paths.
- Invalid source file paths, unsupported file types, insufficient file permissions, encryption failures, or write failures may cause the step to return False.
- This step creates encrypted copies of the source files and does not modify the original files.
- Securely manage encryption keys and decrypted copies in accordance with your organization's security policies.
- The workflow should include appropriate handling for both True and False return paths.
- Encrypting sensitive documents before storage or transmission helps support regulatory compliance, data privacy, and enterprise security requirements.
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 page.
Note: Verify and complete any missing configuration after importing the sample, including:
- Input file paths
- Encrypted output paths
- File mappings
- File system permissions
- Workflow variable definitions
- Environment-specific settings
After verifying the configuration, save the Process Definition before execution.