How does it work?

1. In SFTP To Go, create dedicated credentials for MuleSoft Anypoint Platform 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 MuleSoft:
   • Use password authentication for a standard SFTP connection.
   • Use SSH key authentication if your workflow requires key-based access.
   • Store passwords and private keys in secure configuration properties or a secrets manager rather than in source code.
3. In Anypoint Studio, create a new Mule project for the SFTP To Go integration.
4. In the Mule Palette, search for SFTP and add MuleSoft’s SFTP Connector to the project.
5. Create the SFTP connector configuration:
   • Set Host to the SFTP To Go host.
   • Set Port to 22.
   • Enter the SFTP To Go username.
   • Enter the password or configure the private key file and passphrase for SSH key authentication.
   • Set the working directory if the Mule flow should use a specific folder as the base path.
6. Click Test Connection in Anypoint Studio to confirm that MuleSoft can connect to SFTP To Go.
7. For inbound file workflows, add the On New or Updated File source. Set the directory path that MuleSoft should poll, then configure the scheduling strategy and file handling behavior.
8. Use watermarking or post-processing rules to avoid processing the same file repeatedly. For example, move processed files into an archive folder, or delete them after processing if that matches your retention requirements.
9. Add the required Mule flow steps after the SFTP trigger. Depending on the workflow, this may include transforming file content with DataWeave, sending records to an API, updating a database, creating a message, or passing the file to another connected application.
10. For outbound file workflows, use the SFTP Connector’s Write operation to send files from MuleSoft to SFTP To Go. Set the output path, file name, write mode, and whether MuleSoft should create missing parent directories.
11. Use additional SFTP operations where needed, such as Read, List, Move, Copy, or Delete, depending on how the Mule flow needs to handle files after transfer.
12. Deploy the Mule application through Anypoint Studio, Runtime Manager, CloudHub, CloudHub 2.0, or your chosen MuleSoft deployment environment.
13. Test the integration by uploading a file to the configured SFTP To Go folder using the File Browser or an SFTP client. Confirm that the Mule flow detects the file, processes it, and sends the expected output to the target system or SFTP To Go folder.
14. Monitor the workflow in MuleSoft and review transfer activity in SFTP To Go to confirm successful logins, uploads, downloads, file changes, and access events.

You can find further insight here and here.