How does it work?

1. In SFTP To Go, create dedicated credentials for Boomi to use. Set the required home directory and permissions for the integration, then copy the hostname, port, username, and authentication details from the Credentials tab.
2. Choose the authentication method for Boomi:
   • Use username and password authentication for a standard SFTP connection.
   • Use SSH private-key authentication if your workflow requires key-based access.
   • If using key authentication, configure the key file path or key content in Boomi, depending on how your Boomi runtime is set up.
   • If your SFTP To Go user uses IP restrictions, allow the relevant Boomi Atom, runtime, or cloud attachment outbound address before testing the connection.
3. In Boomi, create a new integration process for the SFTP To Go workflow.
4. Add the SFTP connector to the process. Use it in the Start step for inbound workflows, or as a connector step later in the process for outbound file delivery.
5. Create a new SFTP connection component:
   • Set the host to the SFTP To Go hostname.
   • Set the port to 22.
   • Enter the SFTP To Go username.
   • Enter the password, key file path, or key content according to the authentication method selected.
   • Set the remote directory if the process should work from a specific SFTP To Go folder.
6. If required, configure a Known Host Entry in Boomi so the connector can verify the SFTP To Go server host key during connection negotiation.
7. Click Test Connection to confirm that Boomi can connect to SFTP To Go.
8. For inbound event-driven file workflows, create a Listen operation. Select the SFTP To Go directory or subdirectory that Boomi should monitor.
9. Configure the Listen operation:
   • Select create events if Boomi should process newly uploaded files.
   • Select modify events if Boomi should react when existing files change.
   • Select delete events if Boomi should submit an event when a file is deleted.
   • Set the polling interval according to how often the process should check the remote folder.
10. For inbound batch-style workflows, create a List or Read operation instead of Listen. Use List to return files or file metadata from a folder, and use Read to retrieve the content of a specific file.
11. Set post-processing behavior where needed. For example, after a successful Read, Boomi can leave the file unchanged, move it to another directory, delete it, or rename it.
12. Add the required Boomi process steps after the SFTP operation. Depending on the workflow, this may include mapping file data, applying business rules, transforming records, sending data to an API, updating an application, writing to a database, or routing the file to another connector.
13. For outbound file workflows, add an SFTP connector step with the Write operation. Use this to send files from Boomi to SFTP To Go.
14. Configure the Write operation:
    • Set the target remote directory in SFTP To Go.
    • Set the file name through document properties or the process logic.
    • Choose what should happen if a file with the same name already exists, such as creating a unique name, overwriting, appending, or generating an error.
    • Use a staging directory or temporary extension if the workflow should avoid exposing partially written files.
15. Use separate SFTP To Go folders for incoming files, processed files, archives, failed files, and outbound files. This helps avoid repeated processing and keeps the Boomi process easier to monitor.
16. Test the integration by uploading a file to the configured SFTP To Go folder through the File Browser or an SFTP client. Confirm that Boomi detects, reads, processes, routes, or writes the file as expected.
17. Monitor the process execution in Boomi and review transfer activity in SFTP To Go to confirm successful logins, uploads, downloads, file changes, deletes, and access events.

You can find further insight here and here.