SnapLogic

How does it work?

1. Decide where the file work should happen. Use SnapLogic SFTP Snaps when a pipeline needs to poll, read, or write files. Use SFTP To Go File Automations when files need preparation or follow-up handling in storage. Use Triggered Tasks when a file event should start a SnapLogic pipeline.
2. Create a dedicated SFTP To Go credential for SnapLogic. Bind it to the correct home directory and limit access to the folders used by this pipeline.
3. Copy the SFTP To Go host, username, authentication details, and port from the SFTP connection setup. SFTP To Go uses SFTP port 22 by default.
4. In SnapLogic, create the SFTP account required by the SFTP Snap Pack available in your environment. Configure the host, port, username, password or private key, and any path values your pipeline will use.
5. For inbound files, build the pipeline with the SnapLogic file pattern that fits the job. Use SFTP polling or directory browsing where the pipeline should find files itself, and use a reader step when it should load the file content.
6. For outbound results, write the file back to the correct SFTP To Go folder. Use predictable names so later users, processes, or automations can identify the output.
7. Where SnapLogic should change files as part of the pipeline, use the supported SnapLogic file operation for the task, such as move, copy, rename, or delete. Keep source-file retention and audit requirements in mind before removing or replacing files.
8. Use SFTP To Go File Automations when the file should be handled before SnapLogic reads it or after SnapLogic writes it. Typical actions include copy, move, delete, PGP encrypt, PGP decrypt, delay, notifications, and webhook requests.
9. To let SFTP To Go start a SnapLogic pipeline, first create and test the pipeline in SnapLogic. The pipeline should accept the incoming request, inspect the event payload, and retrieve the file over SFTP when it needs the actual content.
10. Create a SnapLogic Triggered Task for the pipeline. Configure the task URL, Snaplex, authentication method, allowed HTTP method, and response behavior according to your SnapLogic environment.
11. In SFTP To Go, create a webhook notification or File Automation webhook request that calls the SnapLogic Triggered Task URL. Select only the event topics and filters needed for this pipeline.
12. Keep file-event calls selective. Filter by folder, file pattern, actor, or event type, and exclude folder events when the pipeline should only process files.
13. In SnapLogic, route the pipeline from the payload. For example, use file.created for ingestion, validation, or transformation, file.downloaded for audit notifications, and file.deleted for status updates or review paths.
14. If the pipeline needs file content after a webhook, read the file from SFTP To Go using the path in the payload. Decode Data.Path first if the webhook payload uses URL encoding.
15. If SnapLogic 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.
16. Test the full pipeline path. Check inbound pickup, file reads, transformations, output writes, Triggered Task calls, retries, and target system updates.
17. Before production, review SnapLogic Monitor results, pipeline executions, task runs, Snap errors, account settings, and retry behavior alongside SFTP To Go file activity, automation history, webhook delivery, credential access, and audit logs.

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.