SnapLogic

SnapLogic pipelines can read and write Files.com files over SFTP using the Binary Snap Pack. This gives a pipeline access to files collected from partners, customers, and other systems without giving those senders access to SnapLogic or to its destination applications. Files.com owns the exchange folders and their access; the pipeline owns parsing, mapping, and loading the business data.

An SFTP connection works with Files.com paths backed by native storage or a Remote Server Mount. Choose the path according to where the working files should live. Accessing a mounted file operates on the connected storage.

Account and File Address

Use a dedicated Files.com machine account with SFTP enabled. Grant listing and download access to input folders, upload access to output folders, and any additional permissions required by the pipeline's file-management steps.

Attach a suitable SnapLogic account to the Snap. An SSH Auth Account holds the Files.com username and private key, including its header and footer, with a passphrase when required. Register the matching public key on the Files.com user. SnapLogic documents RSA private-key format for this account. A Basic Auth account supports username/password authentication when that matches the Files.com account's configuration.

The Snap's file address combines the SFTP protocol, Files.com hostname, port, and account-visible path. For example, sftp://example.files.com:22/ready/orders.csv identifies one file; replace the example hostname and path with your own. Follow SFTP connection settings for authentication and network requirements. If the account has an SFTP client root, the path starts within that root.

From File Contents to Pipeline Records

File Reader reads a selected file into a binary stream. Follow it with a parser, such as a CSV, JSON, or XML Parser, when the next step needs records. Downloading a CSV does not by itself map its columns or load them into another application.

For a pipeline that processes a collection, Multi File Reader selects files using a directory and wildcard, with an option to include subfolders. Limit that selection to files ready for this pipeline. A recursive selection over both intake and archive directories can submit the same business data again even though the SFTP account has valid access to both.

For example, partners can submit their original files to separate intake folders. A Files.com Automation prepares the required files and publishes them in the pipeline's pickup folder. SnapLogic reads that folder, parses the data, and passes records to the destination connector. The partner accounts and the pipeline account can have different permissions throughout this arrangement.

Output and Completed Work

To publish a result, format the pipeline's records into the required file representation and send that binary output to File Writer. Use a separate output path and a naming policy that distinguishes deliveries. Check the Writer's behavior for an existing destination file before relying on repeated runs.

Keep the decision to archive or remove input after the application step that establishes success. Reading a file proves that the pipeline obtained its contents; a later parse or load can still fail. If a run stops partway through, identify accepted records before repeating the input.

Use SnapLogic's execution records together with Files.com SFTP Logs. Test with a representative file through the parser and destination, including a repeated delivery, so the result establishes both correct mapping and the intended handling of previously processed work.