How does it work?

1. Map the exchange first. Use Babelway’s SFTP Client Gateway In when Babelway should collect files from SFTP To Go, SFTP Client Gateway Out when Babelway should send processed files back, and SFTP To Go File Automations when files need controlled handling before pickup or after delivery.
2. Create a dedicated SFTP To Go credential for Babelway. Bind it to the right home directory and grant only the folder permissions needed for the Babelway channel.
3. Copy the SFTP To Go host, username, authentication details, and port from the SFTP connection setup. Use port 22 unless your SFTP To Go setup requires another supported SFTP port.
4. In Babelway, create or open the channel for this document flow. The channel should define the Gateway In, Message In, Transformation, Message Out, and Gateway Out used for the exchange.
5. For inbound documents, add an SFTP Client Gateway In. Set the SFTP To Go host in Server, enter the Username, configure the password or private key, and set Directory to the folder Babelway should poll.
6. Limit what Babelway imports. Use File pattern for the expected file names or extensions, set a Cron expression where timing matters, and add a Suffix during transfer if files may still be arriving when Babelway checks the folder.
7. Choose the Babelway after-transfer behavior deliberately. Delete removes the source file after Babelway reads it, while Rename, Move, or Move and rename can help separate processed files from new arrivals.
8. Configure the Babelway message steps for the document format. Set Message In, the transformation, and Message Out for the relevant EDI, XML, CSV, Excel, flat-file, UBL, X12, EDIFACT, VDA, or custom format.
9. For outbound documents, add an SFTP Client Gateway Out. Point it to the SFTP To Go output folder, configure the filename, authentication, and retry strategy, and use Filename during transfer where another process might watch the folder.
10. Use SFTP To Go File Automations for file-side preparation or follow-up work. Examples include File created → PGP decrypt → Move before Babelway pickup, or File created → PGP encrypt → Copy → Send webhook request after Babelway delivery.
11. Use SFTP To Go webhooks when another system needs to react to a Babelway file event. Filter by folder, file pattern, actor, or event topic so only the intended B2B files trigger the external process.
12. Use HTTP or REST only for the right job. Babelway can use HTTP or REST gateways, and SFTP To Go can send webhook requests, but webhook payloads describe file events; they do not replace SFTP retrieval when Babelway needs the file content.
13. If Babelway or another workflow service needs to manage SFTP To Go configuration, use the SFTP To Go REST API for supported objects such as credentials, webhooks, share links, audit logs, and audit log exports. Use SFTP, FTPS, HTTPS, or S3 for file content.
14. Test the full exchange. Upload a sample inbound file, confirm that Babelway imports and transforms it, check that the output lands in the correct SFTP To Go folder, and review Babelway message status alongside SFTP To Go file activity, automation history, webhook delivery, and audit logs.

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.