Babelway
SFTP To Go
SFTP To Go is a fully managed secure, scalable, and reliable cloud file storage service supporting SFTP, FTPS, S3, and HTTPS protocols. It allows sharing and integration with third parties using popular and secure protocols, and automates data management and processing using APIs and webhooks.
- Secure data transfer and transparent encryption at rest
- Reliable offsite backup
- Compatibility and ease of use
Babelway
Babelway is a B2B integration and EDI platform from Tradeshift. It uses channels, gateways, message definitions, and transformations to receive business documents, convert them into the required format, and send the result to another system or trading partner. By connecting SFTP To Go with Babelway, you can use managed SFTP storage as the controlled file exchange point for EDI, CSV, XML, flat-file, and other B2B document workflows.
- Let Babelway retrieve inbound files from SFTP To Go using an SFTP Client Gateway In
- Send transformed Babelway output files back to SFTP To Go using an SFTP Client Gateway Out
- Use SFTP To Go File Automations, webhooks, and APIs around the B2B file exchange process
How does it work?
- Decide which file exchange pattern you need. Use Babelway’s SFTP Client Gateway In when Babelway should poll SFTP To Go and retrieve inbound files for processing. Use Babelway’s SFTP Client Gateway Out when Babelway should send transformed output files to SFTP To Go. Use SFTP To Go File Automations when files should be moved, copied, renamed, deleted, encrypted, decrypted, delayed, or routed inside SFTP To Go before or after Babelway processing.
- In SFTP To Go, create or select the credential Babelway should use. Use a dedicated credential for Babelway, bind it to the correct home directory, and give it only the directory permissions required for the channel.
- Copy the SFTP To Go host, username, authentication details, and port by following the SFTP To Go documentation for SFTP connections. SFTP To Go uses port
22by default, with alternative SFTP ports available where needed. - Choose the authentication method Babelway should use to connect to SFTP To Go. For password authentication, store the SFTP To Go username and password in the Babelway gateway settings. For key authentication, use the Babelway private key configuration and add the matching public key to the relevant SFTP To Go credential.
- In Babelway, create or open the channel that should process files from SFTP To Go. A Babelway channel defines the path from the incoming system to the outgoing system, including the gateway in, message in, transformation, message out, and gateway out.
- For inbound files, create a Babelway
SFTP Client Gateway In. Configure theServerwith the SFTP To Go host, set theUsername, add the password or private key, and set theDirectoryto the SFTP To Go folder Babelway should poll. - Set the Babelway file pattern carefully. Use the
File patternfield to limit which files Babelway imports, such as only files ending in.edi,.csv,.xml, or another agreed naming pattern. Keep the pattern narrow enough to avoid processing archive, temporary, or unrelated files. - Configure the Babelway polling schedule. Use the
Cron expressionsetting when Babelway should check SFTP To Go at specific times. If no cron expression is configured, Babelway’s documentation states that the system checks at least once every 15 minutes. - Configure Babelway’s transfer-safety settings. Use a
Suffix during transferwhere appropriate so a file is not processed while still being transferred. Then choose anAfter transfer behaviorthat matches your retention needs. - Do not leave Babelway’s after-transfer behavior on
Deleteunless you really want Babelway to remove the source file from SFTP To Go after reading it. For auditability and recovery, useRename,Move, orMove and renamewhere the original or a processed copy should remain available. - If files need preparation before Babelway imports them, keep that preparation inside SFTP To Go. For example, use SFTP To Go File Automations for
File created → PGP decrypt → Move, orFile created → Rename → Copy, then let Babelway poll the prepared folder. - In Babelway, configure the
Message In, transformation, andMessage Outsteps according to the document format. For example, Babelway can process EDI, XML, CSV, Excel, flat-file, UBL, X12, EDIFACT, VDA, or other supported business document formats depending on your channel design. - For output files, create a Babelway
SFTP Client Gateway Outwhen the transformed message should be delivered to SFTP To Go. Configure the SFTP To Go server, username, password or private key, target directory, output filename pattern, and retry strategy. - Use Babelway’s
Filename during transfersetting where the receiving process should not read an output file before Babelway has finished writing it. This is especially important if another system, user, or automation watches the SFTP To Go output folder. - If files need handling after Babelway writes them to SFTP To Go, use SFTP To Go File Automations on the output folder. For example, use
File created → PGP encrypt → Copy → Send webhook request, orFile created → Move → Send email notification. - If another system needs to know when a file arrives from Babelway, create an SFTP To Go webhook notification or File Automation webhook action. Use topics such as
file.created,file.downloaded, orfile.deleted, and add filters so only the relevant Babelway folders or file patterns trigger the external process. - Use HTTP or REST only where it matches the Babelway channel design. Babelway has HTTP and REST gateway options, and SFTP To Go can send webhook requests, but SFTP To Go webhook payloads describe file events. They do not replace SFTP file retrieval when Babelway needs to process the actual file content.
- If Babelway or another orchestration layer needs to manage SFTP To Go configuration, use the SFTP To Go REST API for supported management tasks such as credentials, public SSH keys, webhooks, share links, audit logs, and audit log exports. Use SFTP, FTPS, or S3 for file content rather than the management API.
- Test the inbound flow by uploading a sample file to the SFTP To Go inbound folder, running Babelway’s connection test or poll function where appropriate, and confirming that Babelway imports the file into the expected channel.
- Test the transformation and outbound flow by confirming that Babelway creates the expected message output and delivers it to the correct SFTP To Go output folder through the SFTP Client Gateway Out.
- Review both systems after the test. In Babelway, check message status, gateway status, channel processing, retry behavior, and errors. In SFTP To Go, check file activity, credential access, automation execution history, webhook deliveries, and audit logs.
- When the flow is ready for production, keep the responsibilities clear. Use Babelway for B2B message transformation, EDI mapping, channel routing, partner document processing, and protocol translation. Use SFTP To Go for managed SFTP access, directory controls, secure storage, storage-side file automations, webhooks, API-driven management, and audit visibility.
You can find further insight into managed SFTP connection setup, SFTP file automations, SFTP webhook notifications, SFTP management APIs, Babelway channel configuration, Babelway SFTP Client Gateway In setup, and Babelway SFTP Client Gateway Out setup.