FTP

Learn how to use the FTP storage action to build your workflow

Introduction

The FTP Storage Action in DBSync Cloud Workflow enables users to upload files directly to an FTP server as part of their integration workflows. This feature is commonly used for transferring data to legacy systems, centralized storage, or other third-party platforms that accept files via FTP.

Use Cases

• Export order or invoice data to an ERP system via FTP.

• Backup integration results to a remote FTP server.

• Share processed reports with partners who use FTP for file exchange.

Use Case Scenario

Scenario: Nightly Order Export to Centralized FTP Server

A retail company uses DBSync to extract completed orders from its eCommerce platform every night. These orders are formatted into a CSV file and need to be transferred to the company's central FTP server for further processing by their ERP system.

Workflow Configuration

1. Query new orders from the eCommerce system.

2. Format the results using a CSV formatter.

3. Use the FTP Storage Action to upload the file to /orders/daily/ on the FTP server.

FTP Action Settings

• Host: ftp.companydomain.com

• Port: 21

• Username/Password: Configured credentials

• Remote Path: /orders/daily/Orders_${date}.csv

• File Content: Output from CSV formatter

• File Type: text/csv

Prerequisites

• Access to a valid FTP server.

• FTP connection configured in DBSync with correct credentials.

• Appropriate write permissions to the target directory on the server.

Configuration Steps

1. Create an FTP Connection

   • Go to the Connections section in DBSync.

   • Select FTP as the connection type.

   • Provide the FTP host, port, username, password, and passive mode setting.

2. Add FTP Storage Action

   • In your workflow, add a new Action Step.

   • Choose FTP Storage from the action types.

1. Set Action Properties

• Remote Path: Define the directory and filename on the FTP server.

• File Content: Map the data or output to be uploaded.

• File Type: Indicate the file MIME type (e.g., text/csv, application/pdf).

• Overwrite: Optionally enable overwriting existing files with the same name.

1. Test and Validate

• Run a test execution of the workflow.

• Verify the file is uploaded to the specified FTP location.

Best Practices

• Use dynamic file naming (e.g., using date or record IDs) to prevent overwriting.

• Confirm directory structure exists on FTP before execution.

• Ensure firewall and network settings allow FTP transfers.

Troubleshooting

• Connection Timeout: Verify FTP server availability and network access.

• Authentication Failed: Check credentials and permissions.

• File Not Appearing: Confirm directory path and test with a manual FTP client.

Limitations

• DBSync supports FTP and FTPS (not SFTP).

• Maximum file size is subject to network and server limits.

• Requires stable internet connectivity during upload.