How does it work?

1. Decide which SnapLogic pattern you need. Use SnapLogic SFTP Snaps when SnapLogic should poll, read from, or write to SFTP To Go. Use a SnapLogic Triggered Task when SFTP To Go should call a pipeline after a file event or File Automation. Use SFTP To Go File Automations when files should be copied, moved, renamed, deleted, encrypted, decrypted, delayed, or routed inside SFTP To Go before or after SnapLogic processing.
2. In SFTP To Go, create or select the credential SnapLogic should use. Use a dedicated credential for SnapLogic, bind it to the correct home directory, and give it only the directory permissions required for the pipeline.
3. 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 SFTP port 22 by default.
4. Choose the authentication method SnapLogic should use to connect to SFTP To Go. For password authentication, use the SFTP To Go username and password in the SnapLogic SFTP account. For key authentication, configure the private key in SnapLogic and add the matching public key to the relevant SFTP To Go credential.
5. In SnapLogic, create the SFTP account or connection required by the SFTP Snap Pack available in your environment. Configure the SFTP To Go host, port, username, authentication method, and any folder path used by the pipeline.
6. If SnapLogic should ingest files from SFTP To Go, build a pipeline with the relevant SFTP read pattern. Depending on the Snap Pack available in your environment, use Snaps such as File Poller, Directory Browser, or File Reader to locate and read files from the SFTP To Go folder.
7. If SnapLogic should deliver output files to SFTP To Go, use the appropriate SFTP write pattern, such as File Writer, and point it to the correct SFTP To Go output folder. Use an output filename pattern that downstream users, systems, or automations can recognize.
8. If SnapLogic should move, copy, rename, or delete files as part of a pipeline, use the appropriate SnapLogic file operation where supported by the Snap Pack and pipeline design. Keep storage-side governance in mind before deleting or replacing source files.
9. If files need preparation before SnapLogic reads them, keep that preparation inside SFTP To Go. For example, use SFTP To Go File Automations for File created → PGP decrypt → Move, or File created → Copy → Send webhook request, then let SnapLogic read from the prepared folder.
10. When using SFTP To Go File Automations, use a trigger such as File created, File downloaded, File deleted, or a schedule. Add a Type is File filter where the workflow should ignore folder events. Then add file actions such as copy, move, rename, delete, PGP encrypt, PGP decrypt, create file or folder, delay, Slack notification, Microsoft Teams notification, email notification, or webhook request.
11. If SFTP To Go should trigger SnapLogic after a file event or File Automation, create and test the SnapLogic pipeline first. The pipeline should accept the incoming request, branch on the event data where needed, retrieve the file through SFTP if file content is required, and return an appropriate response.
12. Create a SnapLogic Triggered Task for the pipeline. SnapLogic Triggered Tasks expose a URL that can invoke a pipeline, and they support HTTP methods including POST. Configure the task, Snaplex, authentication method, and response behavior according to your SnapLogic environment.
13. In SFTP To Go, create a webhook notification or File Automation webhook action that calls the SnapLogic Triggered Task URL. For webhook notifications, choose the endpoint type Webhook, paste the SnapLogic URL, select the relevant topics, and add filters where needed. For File Automations, add a webhook request action after the required file actions have completed.
14. If the SnapLogic Triggered Task requires an authorization header, configure the matching authorization value in the SFTP To Go webhook notification or File Automation webhook action. Keep the task URL, bearer token, or basic-auth value secure because anyone with valid task access can trigger the pipeline.
15. Use SFTP To Go webhook filters to keep SnapLogic triggers narrow. Common filters include path, actor type, actor ID, and file or folder matching rules. For file-only workflows, use a path pattern or a Type is File automation filter so folders do not trigger file-processing logic.
16. In SnapLogic, inspect the incoming request payload when using SFTP To Go webhooks or File Automation webhook actions. For webhook notifications, useful fields include Topic, Data.Path, Data.Size, Actor, and Metadata. For File Automation webhook actions, the payload also includes automation, execution, action, attempt, and idempotency metadata.
17. Branch the SnapLogic pipeline based on the incoming event type. For example, route file.created events to ingestion and transformation steps, file.downloaded events to audit or reporting actions, and file.deleted events to status updates or review tasks.
18. If SnapLogic needs the file content after receiving a webhook, use the SFTP path from the payload to retrieve the file through the configured SFTP Snap. If the payload comes from older SFTP To Go webhook notifications where Data.Path is URL encoded, decode the path before using it in the SnapLogic pipeline.
19. After SnapLogic reads or receives the file reference, continue the pipeline in the systems that need business context. For example, SnapLogic can transform the file, map records, update an application, load a database, call an API, publish to a queue, or route records into another pipeline.
20. If SnapLogic creates an output file that requires storage-side handling, use SFTP To Go File Automations on the output folder. For example, use File created → PGP encrypt → Copy → Send webhook request, or File created → Move → Send email notification.
21. If SnapLogic 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, webhooks, share links, audit logs, and audit log exports. Use SFTP, FTPS, HTTPS, or S3 for file content rather than the management API.
22. Make the integration safe to retry. SFTP To Go webhook and automation delivery can be retried, and SnapLogic tasks or pipelines may also retry depending on their configuration. Use event IDs, delivery IDs, execution IDs, or X-Idempotency-Key values where available to avoid duplicate records, duplicate tickets, repeated loads, or repeated downstream actions.
23. Secure the integration. Use dedicated SFTP To Go credentials, narrow directory permissions, public key authentication where preferred, IP allow lists where appropriate, HTTPS endpoints for webhook calls, SnapLogic task authentication, and signature validation for SFTP To Go webhook requests where your SnapLogic pipeline or fronting service validates signed requests.
24. Test the inbound flow by uploading a sample file to the SFTP To Go inbound folder and confirming that SnapLogic reads it from the expected SFTP Snap, File Poller, Triggered Task, or pipeline step.
25. Test the outbound flow by confirming that SnapLogic writes the expected output file to the correct SFTP To Go folder and that any SFTP To Go File Automation, webhook, notification, or follow-up process runs as expected.
26. Review both systems after the test. In SnapLogic, check task runs, pipeline execution, Snap errors, account configuration, retries, and Monitor results. In SFTP To Go, check file activity, credential access, automation execution history, webhook deliveries, and audit logs.
27. When the flow is ready for production, keep the responsibilities clear. Use SnapLogic for application integration, data integration, transformation, mapping, API-triggered pipelines, and multi-system orchestration. 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, SnapLogic integration platform overview, SnapLogic pipeline design, SnapLogic Custom SFTP Snap Pack, creating SnapLogic Triggered Tasks, SnapLogic task management, and running SnapLogic Triggered Tasks.