Skip to main content

How Files.com Fits With SnapLogic

SnapLogic orchestrates app-to-app and data integration with pipelines built from Snaps. Its SFTP and S3 Snaps read files from, and write files to, a remote endpoint. SnapLogic moves the data well; the part it leaves to you is the heavy, partner-facing file movement underneath — collecting files over SFTP from senders who each use a different format, and getting them clean before a pipeline picks them up.

Files.com is that endpoint. Partners and upstream systems send to your Files.com site over SFTP, FTPS, or HTTPS; an Automation validates each file, normalizes the format, and stages it where the SnapLogic SFTP or S3 Snap reads. The pipeline processes clean data, and the files it writes back are picked up, encrypted, and delivered to each partner — with every transfer logged.

What You Would Use

Be The Endpoint The Snap Hits

Point a SnapLogic SFTP Snap at your Files.com site and it reads and writes staged files over SFTP — one endpoint, per-partner credentials, and an audit record on every transfer.

See File Transfer

Or Connect Over S3

Files.com exposes an S3-compatible API, so a SnapLogic S3 Snap can point at your Files.com site as an S3 endpoint instead of SFTP — no Amazon S3 bucket to provision.

See The S3-Compatible API

Normalize Before The Pipeline

Convert CSV, JSON, XML, and EDI into the shape your pipeline expects, and pull values out of each file to route it, before a SnapLogic Snap ever reads it.

See Transform & Extract

Pre- And Post-Process Around The Run

An Automation validates and stages each arrival before the pipeline runs, and routes or delivers what the pipeline writes after — on a schedule or the moment a file lands.

See Automations

Files.com With SnapLogic FAQ

Put Files.com In The File Path

Receive, transform, route, and audit every file moving to and from SnapLogic — on one platform, with no server of your own to run.

No credit card required • Free for 7 days • Live in minutes