Celigo

Celigo integrator.io flows can use Files.com as their file source and destination through Celigo's FTP connector configured for SFTP. Partners deliver files to Files.com using their own accounts and transfer methods. Celigo collects the prepared input, maps records into the receiving application, and can publish resulting files back to Files.com.

Celigo calls reading from an SFTP server an export, because the file leaves that source. Writing to the server is an import or transfer into the destination. Those names describe a flow step, rather than the business direction of a payroll, order, or accounting feed.

SFTP Connection

Create a dedicated Files.com machine account, enable SFTP, and assign folder permissions for the flow's input and output. Keep partner credentials separate from Celigo's credential so retiring a sender does not interrupt the flow.

In Celigo, create an FTP connection, choose the SFTP protocol, and enter the Files.com hostname, port 22, and username. Select credentials that match the account's authentication method.

For SSH key authentication, Celigo requires an RSA private key in PEM format without a passphrase. Store that private key in Celigo and register its public key on the Files.com user. Celigo's SSH key instructions describe the required format; a .ppk file is not the value to paste into the PEM field.

Check Celigo's User directory is root option against the account's FTP/SFTP folder presentation. For an account whose integration folder appears as /, use paths within that folder instead of repeating its site-wide parent path.

Files or Parsed Records

An FTP export can parse a file into records or transfer its existing contents. Parse it when subsequent application steps need its rows or fields. Use an unchanged file transfer when the receiving system needs the original document, such as a PDF or an already-prepared import package.

Point the export at a ready-for-processing directory and select the intended filename prefix or suffix. Keep retained originals and previously processed files outside that selection. Files.com can handle intake, file transformation, and delivery to other servers while Celigo owns the application's record mapping.

For output, Celigo's FTP import or transfer can generate a file from records or deliver an existing file. Choose the format and final name the consumer expects, and publish output in a different folder from the export's input selection.

Source Retention and Flow Results

Celigo's FTP export deletes source files after transfer unless configured to leave them on the server. Decide that behavior explicitly and grant deletion access only when it is part of the exchange. On a Remote Server Mount, deleting the source acts on the connected storage too; use a separate delivery copy when the original must remain there.

Enabling Leave file on server preserves the files but makes them eligible for another export. Include a deliberate way to distinguish completed work before scheduling repeated runs. Celigo's backup-path option also needs access to its destination folder.

Test a file through the complete flow and inspect the receiving application's result. If an application step fails after Celigo collected the file, check source retention and completed records before resubmitting it. Celigo's flow results and Files.com SFTP Logs identify different stages of that exchange.