Workato

Workato recipes can read, write, and manage files on Files.com through Workato's SFTP connector. Files.com receives files from partners and systems through the methods they use, while the recipe coordinates application calls, field mapping, and business processing. The recipe sees one file endpoint even when the senders use different protocols or upload through a browser.

This arrangement uses Workato's SFTP connector. It does not require a dedicated Files.com connector or a Files.com API key. The connection authenticates as a Files.com user whose SFTP access and folder permissions determine what the recipe can do.

Recipe Connection

Create a dedicated machine account, enable SFTP, and grant the operations the recipe needs. Listing and download access support collection; upload access supports publishing a result. Moving files requires the appropriate access to both source and destination folders.

Use these values in Workato's SFTP connection:

Use folder paths as they appear to the account. If an SFTP client root presents the integration folder as /, recipe actions use paths inside that root. They do not include the site's original parent path.

File Preparation and Application Work

Let Files.com own the file operations that belong around the recipe, such as receiving submissions, applying GPG decryption, or delivering output to a recipient's server. Keep application decisions in Workato when the next action depends on a CRM record, an approval, or another application's response.

For example, a partner can upload an encrypted order file to its intake folder. Files.com decrypts it and publishes the prepared result in a recipe pickup folder. Workato downloads that file and creates the application's records, then publishes a response file to a separate output folder. The partner's account needs access to its submission and response; it does not need the recipe's access or the business application's credentials.

This division is a design choice. A recipe can perform file preparation itself when that is where the existing workflow owns it. Configure the selected stages explicitly rather than assuming that a file is decrypted, validated, or routed because it reached Files.com.

Recipe Triggers and File Readiness

Workato's new or updated file trigger watches only the first level of the selected directory. Point it at the prepared folder, keep temporary and archive files outside it, and use a Download File action to retrieve the reported file's contents. Choose the initial pickup time to include the deliveries the recipe should process; connecting successfully does not mean older files have been selected.

A Files.com Webhook can instead notify a recipe configured to accept an incoming HTTP request. The notification identifies file activity; the recipe still needs to retrieve the file and handle repeated or already-processed work. Choose this arrangement when the recipe should react to a supported event rather than discover files on its SFTP trigger schedule.

For files published to a Remote Server Mount, a successful upload can precede buffered onward delivery. Verify the stage required by the next consumer before treating the recipe's publication as completed delivery.

Job Results

Test a representative file through both the SFTP action and the application action it starts. Confirm the Files.com path and contents, the Workato job result, and the receiving application's outcome. A successful file download does not establish that the subsequent application call succeeded.

Use Workato's job history with Files.com SFTP Logs to separate connection errors from recipe failures. If the next file never arrives, an Expectation can report the missing input independently of whether a recipe job started.