Jitterbit operations read and write files through FTP endpoints. Point the endpoints at Files.com and the file layer under your projects becomes managed: partner intake, PGP, transformation, and monitoring built in, with operations kept for the mapping work they’re good at.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Jitterbit’s FTP connector is clean: a connection, Read activities as sources, Write activities as targets. What the connector reads is only as good as the endpoint behind it — and that endpoint usually arrives as a server somebody stands up for the project, feeds by hand, and forgets, with every counterparty quirk landing raw in operation logic.
Files.com is the endpoint with the File Orchestration Platform already underneath. Counterparties deliver into scoped folders, PGP runs as configuration, TransformScript shapes files before operations read them, and monitoring catches the feed that would have fed the project silence.
Endpoints for operations, intake before the mapping, and monitoring on every source.
In Jitterbit, an FTP endpoint is a connection plus its Read and Write activities, used as sources and targets for operations. Point the connection at Files.com and every operation gets a managed cloud SFTP endpoint your team never patches or babysits.
The files an operation processes start at counterparties. Each delivers into its own scoped folder over SFTP, FTPS, AS2, or a browser. The Read activity sweeps a clean staging folder, not a shared dumping ground.
Renaming, splitting, format conversion, and per-recipient encryption run as Automations and TransformScript on the platform. Operations keep their transformation power for the record-level mapping they’re built for.
Counterparty encryption runs as folder settings with keys in one key manager. Files decrypt before a Read activity touches them and encrypt after a Write, with no key handling inside the project.
Jitterbit rarely runs alone: ERPs, banks, and vendor systems all move files around it. One Files.com site carries the whole exchange under one audit trail, with each relationship separately scoped.
An operation reading an empty folder succeeds at processing nothing. Delivery monitoring knows the window each upstream feed is due in and raises an alert when that window closes without a file.
What the connector’s own docs ask for at setup, answered on the Files.com side.
Host, port, and a credential: password or SSH client key for SFTP. Files.com issues a scoped service user per project, and the permanent hostname and host key never rotate out from under a connection.
Give inbound and outbound activities their own folders and service users. The audit trail then reads per-direction, and a credential rotation touches exactly one side of one project.
Counterparties that mandate FTPS, plain FTP, or AS2 deliver into the same folders the operations read over SFTP. The partner’s protocol never enters the project.
Files.com webhooks fire on upload events, so an API-triggered operation can start the moment a counterparty’s file lands instead of on the next schedule.
“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 Jitterbit operations.
Jitterbit connects to Files.com through the standard FTP connector in Integration Studio: a connection with host, port, and a credential (password or SSH client key), plus Read and Write activities used as operation sources and targets. Files.com’s permanent hostname and host key mean the connection outlives every change behind it.
Jitterbit Read activities pull files from Files.com as operation sources, and Write activities deliver files back as operation targets. Scripts can call both. Files.com folders serve as the file workspace on either side of any operation.
Keep Jitterbit’s transformation for record-level mapping. That’s what it’s built for. File-shaped work (format conversion, splitting, renaming, per-recipient encryption) runs as TransformScript and Automations on the platform, as configuration.
Files.com handles PGP. Encryption and decryption run as folder settings, with every key in the Files.com key manager. Operations read and write plain files, and no private key lives in a project.
Counterparties deliver to Files.com however they can: SFTP, FTPS, FTP, AS2, the S3-compatible API, a browser, or an email inbox that turns attachments into files. Each sender gets its own scoped credential and folder.
When the operation is really file movement with transformation (pick up, convert, rename, deliver), yes: a Files.com Automation covers it, with one less operation to maintain. Jitterbit stays for the work that touches APIs and business records.
Yes. Files.com webhooks fire on upload events, so an API-triggered operation starts the moment a file lands instead of waiting on the next scheduled run.
Files.com delivery monitoring defines the window each feed is due in and raises an alert when a window closes without files, so the operation that quietly processed nothing gets noticed.
Yes. Files.com holds SOC 2 Type II and offers a pre-approved HIPAA business associate agreement with Files.com Enterprise. Files are encrypted in transit and at rest, folders are least-privilege, and the audit log records every file an operation read or wrote.
Files.com replaces the bare SFTP server the operations were pointed at, and everything it lacked: partner onboarding, key management, transformation, monitoring, and an archive. The projects keep working; the layer under them becomes a service.
Files.com manages partner intake, every protocol, PGP, and transformation underneath Jitterbit, so operations do only the mapping.
No credit card required • Free for 7 days • Live in minutes