Import files to an FTP server

Create FTP imports:

1. To configure the FTP import on the Integration App, navigate to Tools menu > Flow builder and click + Destination applications.
2. Select Import data into destination application.

3. From the Application dropdown, select FTP as the destination application and the required FTP connection.
4. Click Next.
5. Create or select an FTP connection.

Configuring the FTP import fields:

• Name (required): Name your import so that you can easily reference it from other parts of the application.
• Description (optional): Add an easily-understood description to the import. This is to help other users understand what it’s doing without having to read through all the fields and settings.  
• Input mode (optional): This field determines what type of information will be imported. ie., Records or Blob Keys.
• Directory Path (required): This field specifies the directory path of the files you want imported into the FTP folder. For example: \Parent Directory\Child Directory.

• File Type (required): Select the type of files that you want to generate. The file types available for FTP exports are listed below:
  • CSV
  • JSON
  • XLSX
  • XML
  • EDI X12
  • FIXED WIDTH
  • EDIFACT 

For example, if you are importing CSV files (i.e. files containing Comma Separated Value data) then please choose CSV. 

Get more info on FTP EDI imports. 

• File Name (required): Use this field to specify how the files being uploaded to the FTP site should be named. Note that some filesystems do not allow special characters like colons (:) in the filenames.
  
  You can type '{{{' to include a predefined timestamp template in your file name. For example, 'FileXYZ-{{{timestamp(YY-MM-DD)}}}.txt' will upload files with the following pattern: 'FileXYZ-16-06-30.txt'. 
  
  
• Upload a sample file (optional): You can provide a sample file that this import processes. It will use the sample file to auto-set fields where possible and helps you map data.

• CSV generate options: You can configure the CSV generate options based on the requirement(s).

• Column delimiter: Select the column delimiter that you are using in the files to be imported. For example: comma, space, semicolon, pipe, or tab.
• Row Delimiter: Select the row delimiter to be used in the file to be imported.
  Ex: '\n', '\r\n', '\r' (Default is CRLF)
• Include Header: Set this field to True to include a top-level header row in your CSV file (i.e. the very first row in your CSV file will be a set of column names so that anyone reading the CSV file can quickly understand what each column represents).
• Truncate last row delimiter: Set this field to True if you want to truncate the last row delimiter (Default is False)
• Replace tab with space: When this field is set to True, tabs in the content of the data (except columnDelimiters) are replaced with a space (Default is False)
• Wrap with quotes: When this field is set to True, all the values in the file are wrapped with quotes (Default is False).
• Replace new line with space: When this field is set to True, new lines in the content of the data (except rowDelimiters) are replaced with a space (Default is False)
• Flow data:  The data from the uploaded sample file will be shown here.
• Generated result: The result generated after applying all the settings on the sample data will be shown here.
• Does each individual record being processed translate to multiple records in the import application?: We use this field to simplify the export data, based on the requirement you can set it to True (Default is False). 

Advanced Settings

The advanced setting contains the following settings:

• Encrypt files: If the connection you selected is configured to use PGP, this option is available. When selected, additional options appear. See Enable PGP encryption/decryption in file exports and imports.
• Use temp file while upload in progress (optional): Some FTP sites require that a file use a temporary file name pattern while an upload is in progress, and then after an upload is complete, that a file is renamed to officially let the FTP site know that no more data is expected, and that the file can safely be processed by another application.
• Backup files path (optional): Enter a value relative to the file system’s root directory, if you want to archive a copy of the exported files. For example, to instruct integrator.io to store a copy of the imported file at ftps://ftp.my-site.com/integrations/backup, enter /integrations/backup. This path must already exist on the server. 
• File encoding: The file encoding indicates how the individual characters in your data are represented on the file system. Depending on the source system of the data, the encoding can take on different formats. If left blank, the default encoding is UTF-8, but you can also choose Windows-1252 or UTF-16LE formats.
• Skip aggregation (optional): By default, Celigo integrator.io will aggregate all the pages of data that get generated by an export into one (possibly large) file. If you prefer multiple smaller files (vs. one large file), then set this field to True. This setting is not available for file types EDIFACT, EDI X12, and Fixed-Width.
• Compress files (optional): If you would like to compress files before they are posted to the import application, set this field to True. Once you check this field, a dropdown field appears for you to choose the compression format:
• Invoke: This resource can be invoked via an HTTP POST request to this unique url.

Saving the import

Once you are done with configuring all the fields on the import form, click Save to save the FTP import.