Workato recipes read and write files through an SFTP connector. Point that connector at Files.com, the File Orchestration Platform, and the file layer under your recipes becomes managed: partner intake, endpoints Workato doesn’t host, PGP, transformation, and audit. Recipes keep the work only an iPaaS does well.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
An iPaaS earns its keep on API-object work: create the Salesforce record, update the NetSuite object, map the fields between them. The file side of integration is a different job: counterparties with protocol mandates, feeds that arrive encrypted, large payloads, and the audit trail someone eventually asks for. Building that side out of recipe steps means task counts spent on busywork and partner quirks hardcoded into flows.
Files.com runs the file layer, and Workato keeps the work it’s actually best at. Recipes read and write one managed endpoint; partner onboarding, AS2 and EDI, PGP, and transformation run as platform configuration underneath. When a flow is really just file movement, an Automation replaces the recipe outright.
The work that moves off your recipes and onto the platform underneath.
Workato’s SFTP connector triggers on new or updated files and runs upload, download, move, and list actions. Point it at a Files.com folder and every recipe gets a managed SFTP endpoint: a permanent hostname and host key, concurrent sessions, and no server of yours behind it.
The files a recipe processes start at counterparties. Each one delivers into its own scoped folder over SFTP, FTPS, AS2, or a browser, so the recipe reads one clean staging folder instead of juggling every partner’s quirks in recipe logic.
Format conversion, splitting, renaming, and per-recipient encryption run as Automations and TransformScript on the Files.com side: platform configuration, not recipe steps.
A file landing on Files.com can fire a webhook that starts a recipe the moment data arrives. The flow runs on events instead of polling, and the API side of the work begins exactly when the file side is ready.
Workato’s connectors are clients: a recipe can reach out to a server, but a counterparty has nowhere to push a file. When a partner mandates AS2 with signed receipts or delivers over plain FTP, Files.com carries the protocol and hands the recipe an ordinary file, so the partner’s mandate never becomes the recipe’s problem.
Recipes come and go; auditors ask what moved. Every read, write, decryption, and delivery lands in the audit log, with retention policies keeping originals as long as compliance wants them.
What Workato’s SFTP connector asks for at setup, answered on the Files.com side.
Host, port 22, and a credential (password or a private key in OpenSSH format), plus the host key fingerprint. Files.com’s host key is permanent, so the fingerprint you configure at setup never rotates out from under your recipes.
Workato’s cloud connector declines SSH-RSA because of its SHA-1 weakness. Files.com negotiates modern key exchange and ciphers, so the cloud connection works without deploying an on-prem agent to tolerate old cryptography.
Give each recipe family its own Files.com service user scoped to its own folder. Rotating one credential touches one set of recipes, and the audit trail reads per-integration.
The connector’s new/updated file trigger and batch CSV trigger poll the folder; Files.com webhooks can start recipes event-driven instead. Either way, files land whole before processing begins.
“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 Workato recipes.
Workato connects to Files.com through its standard SFTP connector: hostname, port 22, and a password or OpenSSH-format private key, plus the host key fingerprint. Files.com’s hostname and host key are permanent, so the connection you configure once keeps working through every change behind it.
A recipe can do everything the SFTP connector offers against Files.com: trigger on new or updated files (including the batch CSV trigger) and run upload, download, move, rename, delete, list, and search actions. Recipes treat Files.com folders as their file workspace.
Run file transformation in Files.com and keep Workato on the work only an iPaaS does well: API-object integration and field mapping into your SaaS systems. Format conversion, splitting, renaming, and per-recipient encryption run as TransformScript and Automations on the Files.com side, as configuration rather than recipe steps consuming tasks.
Yes. Files.com webhooks fire on upload events, so a recipe starts the moment a counterparty’s file lands instead of on the next poll. The connector’s own triggers work too, for teams that prefer polling.
Files.com carries the protocol and the recipe never sees it. AS2 with signed MDN receipts, FTPS, plain FTP for the legacy counterparty, the S3-compatible API, and browser upload all land files in the same folders the recipe reads.
Workato’s cloud connector works directly with Files.com. Workato declines SSH-RSA on cloud connections because of its SHA-1 weakness. Files.com negotiates modern ciphers, so no on-prem agent is needed to tolerate old cryptography.
Files.com handles PGP, not the recipe. Encryption and decryption run as folder settings with every key in the Files.com key manager. Recipes read and write plain files, and no private key lives in a recipe step.
Yes. When the recipe is really just file movement (pick up, convert, rename, deliver), a Files.com Automation covers it with no Workato tasks consumed and one less recipe to maintain. Workato stays for the work that touches APIs and business objects.
Files.com raises an alert when a feed’s delivery window closes without a file. A Workato trigger that never fires makes no noise. Delivery monitoring defines when each feed is due, so the recipe that didn’t run gets noticed before its downstream deadline does.
Yes. A pre-approved HIPAA business associate agreement comes with Files.com Enterprise. The platform runs SOC 2 Type II, encrypts in transit and at rest, and records every access in the audit log. The governance holds however a file arrives and whichever recipe touches it.
Partner intake, every protocol, PGP, transformation, and audit, managed underneath Workato. Recipes keep only the work an iPaaS is built for.
No credit card required • Free for 7 days • Live in minutes