Be The Endpoint Workato Connects To
Point the Workato 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 Workato
Workato automates app-to-app work with recipes, and its SFTP connector reads files from, and writes files to, a remote host. The recipe logic is the easy part. The part that breaks is the file movement underneath it: partners send over SFTP in formats that vary by sender, and each file has to be collected, validated, and cleaned before a recipe ever picks it up.
Files.com is that host. 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 Workato SFTP connector reads. The recipe runs against clean data, and the files it writes back are picked up, encrypted, and delivered to each partner — with every transfer logged and each partner scoped to its own folder.
What You Would Use
Or Connect Over S3
Files.com exposes an S3-compatible API, so where a Workato recipe 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 Recipe
Convert CSV, JSON, XML, and EDI into the shape your recipe expects, and pull values out of each file to route it, before the Workato connector ever reads it.
See Transform & ExtractPre- And Post-Process Around The Run
An Automation validates and stages each arrival before the recipe runs, and routes or delivers what the recipe writes after — on a schedule or the moment a file lands.
See AutomationsFiles.com With Workato FAQ
Put Files.com In The File Path
Receive, transform, route, and audit every file moving to and from Workato — on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes