Tray workflows read and write files through the FTP Client connector. Point the connector at Files.com and the file layer under your workflows becomes managed: partner intake, PGP, transformation, and event-driven triggers built in.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Tray’s FTP Client connector gives workflows the verbs: upload, download, list, move, check. What it doesn’t give them is the noun: the endpoint itself, with the partner credentials, the keys, the transformation, and the monitoring a real counterparty exchange needs. Built from workflow steps, that layer turns into polling loops and per-sender special cases.
Files.com is the noun — the managed layer the verbs act on. Counterparties deliver into scoped folders, PGP runs as configuration, webhooks start workflows the moment files land, and monitoring catches the trigger that never fired.
A managed endpoint for workflows, events over polling, and transformation off the step count.
Tray’s FTP Client connector uploads, downloads, lists, moves, and checks files over SFTP. Point it at Files.com and every workflow gets a managed endpoint: permanent hostname, scoped credentials, and no server of yours behind it.
The files a workflow processes start at counterparties. Each delivers into its own scoped folder over SFTP, FTPS, AS2, or a browser. The workflow reads one clean staging folder instead of handling every sender’s quirks in steps.
Files.com webhooks fire on upload events into a Tray webhook trigger, so a workflow starts the moment a counterparty’s file lands, instead of polling with list-and-check steps.
Format conversion, splitting, renaming, and per-recipient encryption run as Automations and TransformScript on the platform, so workflows stay short and their steps stay on the API work they’re for.
Counterparty encryption runs as folder settings. Files decrypt before the workflow downloads them and encrypt after it uploads, with every key in one place and none in a workflow step.
A workflow waiting on a file that never arrives waits silently. Delivery monitoring knows when each upstream feed is due and raises an alert when a window closes without its file.
Tray asks for a host and a credential. The endpoint behind them is the part your team lives with.
Host, port, and a credential for the FTP Client connector. Files.com issues a scoped service user per workflow family, on a permanent hostname with a host key that never rotates out from under the connection you configured.
Each set of workflows gets its own Files.com service user scoped to its own folders, so one rotation touches one family and the audit trail reads per-integration.
Counterparties that mandate FTPS, plain FTP, or AS2 deliver into the same folders the workflow reads over SFTP, so the partner’s protocol never becomes a workflow’s problem.
Files.com holds single files up to 5 TB. Moves, renames, and file-exists checks run on the server itself, so a workflow can route a warehouse export that would never fit through a step payload without ever carrying its bytes.
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What integration teams ask most when wiring file work into Tray workflows.
Partner intake, every protocol, PGP, and event-driven triggers: all managed underneath Tray, so workflows do only the API work.
No credit card required • Free for 7 days • Live in minutes