Be The Endpoint Celigo Connects To
Point the Celigo FTP/SFTP connector 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 TransferHow Files.com Fits With Celigo
Celigo connects applications with integration flows, and its FTP/SFTP connector reads files from, and writes files to, a remote endpoint. The flow handles the app-to-app mapping. The part it leaves to you is the partner-facing file movement underneath: files arrive over SFTP from senders who each use a different format and schedule, and each one has to be collected, validated, and cleaned before a flow picks it 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 Celigo FTP/SFTP connector reads. The flow runs against 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
Or Connect Over S3
Files.com exposes an S3-compatible API, so where a Celigo flow prefers S3, it points at your Files.com site as an S3 endpoint instead of SFTP — no Amazon S3 bucket to provision.
See The S3-Compatible APINormalize Before The Flow
Convert CSV, JSON, XML, and EDI into the shape your flow expects, and pull values out of each file to route it, before the Celigo connector ever reads it.
See Transform & ExtractPre- And Post-Process Around The Run
An Automation validates and stages each arrival before the flow runs, and routes or delivers what the flow writes after — on a schedule or the moment a file lands.
See AutomationsFiles.com With Celigo FAQ
Put Files.com In The File Path
Receive, transform, route, and audit every file moving to and from Celigo — on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes