File
Learn how to use the File storage action to build your workflow
Introduction
The File storage action in DBSync Cloud Workflow allows users to store file-based data generated during workflow execution. This feature is useful for archiving, transferring, or later processing data such as CSVs, JSON, or XML documents. It provides flexibility to manage files within the context of a data integration or automation process.
Use Cases
Storing intermediate transformation results
Archiving transaction data
Exporting data for manual review
Sending files to third-party systems via APIs or file transfer
Configuration Steps
Add the File Storage Action
In your Cloud Workflow designer, click on "+ Add Action."
Select File from the list of available actions.
Configure File Name and Format
Provide a name for the file.
Select the desired file format (e.g.,
.csv,.json,.xml).You may use dynamic placeholders (e.g.,
${date}or${recordId}) to create unique file names.
Specify File Content
Map the data or variables from earlier actions to be written to the file.
Ensure the content format matches the selected file type.
Select Storage Destination
Choose the storage location:
Internal storage (default DBSync file system)
External cloud storage (e.g., AWS S3, Azure Blob Storage, Google Cloud Storage)
Provide authentication and path details if using external storage.
Set File Options (Optional)
Overwrite existing files (Yes/No)
Enable compression (e.g.,
.zip,.gzip)Enable encryption, if supported
Execution Behavior
During workflow execution, DBSync will create and save the file at the specified location.
Errors in file creation (e.g., permission denied, invalid path) will be logged and can trigger retry logic or error handling paths.
Best Practices
Use consistent naming conventions to keep files organized.
Leverage timestamp placeholders for versioning.
Secure credentials when using external storage locations.
Validate output by enabling logging or audit trails.
Limitations
File size limits may apply depending on the chosen storage.
External storage integrations may require additional setup.
Format conversion should be handled explicitly in data preparation steps.
The File storage action provides a powerful mechanism to handle file output within DBSync workflows, supporting a wide range of use cases from backup to system integration. Proper configuration ensures reliable and secure file management as part of your automation strategy.
Last updated