Skip to main content

ShareFile

Connect ShareFile through its implicit FTPS serviceExternal LinkThis link leads to an external website and will open in a new tab when a partner or team keeps the files your workflow needs there. Configure an FTP Remote Server with Require SSL (Implicit) on port 990. ShareFile's service uses TLS, rather than SFTP over SSH.

This is a protocol-based connection, rather than a native ShareFile API connector. We recommend recurring Syncs for file delivery and collection, with subsequent processing on the delivered copy, because ShareFile's connection and command limits can interrupt work against its endpoint.

Connecting to ShareFile

Enable FTPS access in the ShareFile account before configuring the connection.

When configuring the Remote Server, use the hostname format subdomain.sharefileftp.com, where subdomain is your ShareFile account subdomain. Enter the username in the format subdomain/emailaddress, such as acme/jsmith@acme.com. Use the ShareFile password or, when multi-factor authentication is enabled, a ShareFile application-specific passwordExternal LinkThis link leads to an external website and will open in a new tab. A browser SSO session does not supply the FTPS credential.

ShareFile documents a limit of 8 simultaneous FTP connections per user and applies command throttling as operation counts increase. These limits can slow or interrupt file transfers even when the Files.com connection is configured correctly.

When configuring the FTP Remote Server connection to ShareFile, set Max connections to 1 to reduce concurrent requests to ShareFile. Increase it cautiously only after transfers run reliably; we have seen problems even at 2 connections.

Recurring Transfers

Use a recurring Sync to move or copy files between ShareFile and Files.com. Each run compares source and destination and transfers files that are missing or differ in size. If the provider interrupts a transfer or temporarily limits the connection, a later run can detect files that still need to transfer. This recurring comparison makes Sync a better fit for these endpoint limitations.

We do not recommend running Automations directly against the ShareFile connection. For workflows that process incoming files, Sync them into Files.com storage first, then run Automations on those local files. This keeps subsequent processing from depending on the provider's connection availability and transfer speed.