How does it work?

1. Choose the workflow pattern. Use SFTP To Go webhooks for direct file-event triggers, File Automations for storage-side handling before n8n runs, n8n’s FTP node for SFTP file access, or the SFTP To Go REST API for supported management tasks.
2. In SFTP To Go, create a dedicated credential for n8n. Copy the host, username, authentication details, and port from the SFTP connection setup, and keep folder permissions as narrow as the workflow allows.
3. In n8n, create an FTP credential for SFTP access. Use the SFTP To Go host, port, username, and password or key-based authentication.
4. Add n8n’s FTP node when the workflow needs file access. Use the relevant operation, such as List, Download, Upload, Delete, or Rename or move, and point it to the correct SFTP path.
5. To trigger n8n from SFTP To Go, create an n8n workflow with a Webhook node. Set the HTTP method to POST, choose a clear path, and configure authentication if required.
6. Use the n8n test webhook URL while building. Once the workflow is active, switch the SFTP To Go webhook notification or File Automation endpoint to the production webhook URL.
7. In SFTP To Go, create either a webhook notification for upload, download, or delete events, or a File Automation with an event or schedule trigger followed by the required file actions and a webhook request to n8n.
8. Keep triggers specific. Use SFTP To Go filters such as path, actor type, actor ID, or file pattern, and exclude folder events for file-only workflows.
9. Use SFTP To Go File Automations for storage-side steps such as copy, move, delete, PGP encrypt, PGP decrypt, delay, notifications, or webhook requests before n8n handles app logic.
10. In n8n, inspect the incoming payload. Use fields such as Topic, Data.Path, Data.Size, Actor, Metadata, and automation or idempotency metadata where available.
11. Branch the n8n workflow by event type. For example, send file.created to validation or processing, file.downloaded to audit alerts, and file.deleted to status updates or review tasks.
12. If n8n needs file content, download it from SFTP To Go with the FTP node using the path from the payload. Decode Data.Path first if the payload uses URL encoding.
13. If n8n creates a return file, upload it to the right SFTP To Go path with the FTP node. Use SFTP To Go File Automations for follow-up handling such as move, copy, delete, encrypt, decrypt, notify, or webhook request.
14. Before publishing, test uploads, downloads, deletions, schedules, webhooks, FTP actions, API calls, retries, and target app updates. Review SFTP To Go webhook deliveries, automation history, credential activity, and audit logs alongside n8n workflow executions and failed nodes.

You can find further insight into SFTP webhook notifications, SFTP file automations, SFTP management APIs, n8n Webhook node setup, n8n FTP node for SFTP file transfers, and n8n HTTP Request node API workflows.