Celigo integrator.io flows read and write files through SFTP/FTP connections. Point the connections at Files.com and the file layer under your flows becomes managed: partner intake, PGP in one key manager, transformation as configuration, and monitoring that catches the feed that never arrives.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
An iPaaS earns its keep on record-level work: read the file, map the fields, create the NetSuite transaction. The file side of the same integration is a different job. Counterparties arrive with protocol mandates, PGP keys get pasted connection by connection, and an SFTP server somebody has to run sits under it all for the flows to poll. Building that side out of flow steps hardcodes every partner quirk into the integration.
Files.com runs the file layer, and Celigo keeps the mapping. Flows read and write one managed endpoint. Partner onboarding, PGP, transformation, and monitoring run as platform configuration underneath. When a flow is really just file movement, an Automation replaces it outright.
A managed endpoint for flows, intake before the mapping, and PGP off the per-connection treadmill.
Every integrator.io flow that touches files does it through an SFTP or FTP connection. Files.com gives those connections a managed endpoint: permanent hostname, scoped credentials, concurrent sessions, and no server of yours behind it.
The files a flow processes start at counterparties. Each delivers into its own scoped folder over SFTP, FTPS, AS2, or a browser. The flow reads one clean staging folder instead of carrying every partner’s quirks in its own logic.
Celigo’s PGP runs per connection, with keys you generate elsewhere and paste in. Or Files.com handles PGP as folder settings: one key manager for every counterparty, and the flow reads plain files.
Renaming, splitting, format conversion, and routing run as Automations and TransformScript on the platform. Flows stay focused on the record-level mapping they’re good at.
Your stack mixes an iPaaS with ERPs, banks, and in-house systems. One Files.com site carries all of it under one audit trail: the flows, the scheduled feeds, and the counterparties.
A flow polling an empty folder reports nothing wrong. Delivery monitoring knows when each upstream feed is due and alerts when a window closes without a file, before the missing records reach anyone’s dashboard.
What Celigo’s connection setup asks for, answered on the Files.com side.
Host, credentials, and a private key in PEM format for SFTP key auth. On the Files.com side that means a permanent hostname and a host key that never rotate out from under the connection.
Give each integration its own Files.com service user scoped to its own folders: one credential rotation touches one set of flows, and the audit trail reads per-integration.
Counterparties that mandate AS2, FTPS, or plain FTP deliver into the same folders the flow reads over SFTP. The partner’s protocol never becomes the flow’s problem.
Files.com webhooks fire on upload events, so downstream processing can start the moment a counterparty’s file lands instead of on the next polling interval.
The replacement had to schedule both retrieval and cleanup without installing software or changing anything inside the vendor-controlled payroll platform.
“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 Celigo flows.
Partner intake, every protocol, PGP, and transformation, all managed underneath Celigo, so flows do only the work an iPaaS is built for.
No credit card required • Free for 7 days • Live in minutes