How does it work?

1. Decide which integration pattern you need. Use SFTP To Go webhooks when Azure Logic Apps should react to file events. Use SFTP To Go File Automations when files should be moved, copied, deleted, encrypted, decrypted, delayed, or otherwise handled inside SFTP To Go before Azure Logic Apps is triggered. Use the Azure Logic Apps SFTP-SSH connector when the workflow needs to connect to SFTP To Go storage directly. Use the Azure Logic Apps HTTP action when the workflow needs to call the SFTP To Go REST API.
2. In Azure, create or open the Logic Apps workflow that should receive SFTP To Go file events. For an event-driven workflow, start with the Request trigger named When a HTTP request is received.
3. In the Request trigger, set the method to POST. Add a request body JSON schema if you want Azure Logic Apps to expose SFTP To Go payload fields as workflow tokens. You can generate the schema from a sample SFTP To Go webhook or File Automation payload.
4. Save the Logic Apps workflow. Azure generates the HTTP URL only after the workflow is saved. Copy this generated URL and keep it secure because it is the endpoint SFTP To Go will call.
5. In SFTP To Go, decide whether to use a standard webhook notification or a File Automation. For a direct event trigger, create a webhook notification for file upload, file deletion, or file download events. For a controlled file process, create a File Automation with the required event or schedule trigger, add the file actions in the order they should run, and finish with a webhook request to the Logic Apps Request trigger URL.
6. When using SFTP To Go webhook notifications, choose the endpoint type Webhook, paste the Azure Logic Apps URL, select the relevant topics, and add filters where needed. Use filters such as path, actor type, actor ID, or file pattern to prevent unrelated file activity from triggering the Logic Apps workflow.
7. 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, delete, PGP encrypt, PGP decrypt, delay, Slack notification, Microsoft Teams notification, email notification, or webhook request.
8. If the file should be prepared before Azure Logic Apps acts on it, keep that file handling inside SFTP To Go. For example, use File created → PGP decrypt → Move → Send webhook request, or Scheduled trigger → PGP encrypt → Copy → Send webhook request. Then let Azure Logic Apps handle the external app and Azure service logic after the file is ready.
9. Generate a test event in SFTP To Go by uploading, downloading, deleting, or scheduling a test file. Confirm that the Logic Apps workflow run starts and receives the request payload.
10. In Azure Logic Apps, inspect the incoming payload from the Request trigger. For SFTP To Go webhook notifications, useful fields can 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.
11. Branch the workflow based on the incoming event. For example, route file.created events to validation and processing steps, file.downloaded events to audit notifications, and file.deleted events to record updates or review tasks.
12. If the Logic Apps workflow needs direct file access, create an SFTP-SSH connection to SFTP To Go. In SFTP To Go, create or select the credential Azure Logic Apps should use and copy the SFTP host, username, authentication details, and port by following the SFTP To Go documentation for SFTP connections.
13. In Azure Logic Apps, add the SFTP-SSH connector action that matches the workflow. Common actions include getting file content by path, creating a file, copying a file, deleting a file, listing folder contents, or getting file metadata. Use the path from the SFTP To Go webhook payload when the workflow needs to act on the triggering file.
14. If Azure Logic Apps should monitor SFTP To Go by polling instead of receiving SFTP To Go webhooks, use an SFTP-SSH trigger such as When a file is added or modified. Use this pattern only when polling is the right fit for the workflow. For event-driven workflows, prefer SFTP To Go webhooks or File Automations.
15. If the Logic Apps workflow creates a file that must return to SFTP To Go, use the SFTP-SSH connector to write the file to the correct SFTP path. Where the return file requires storage-side handling such as archive, move, copy, delete, encrypt, or decrypt, keep those actions in SFTP To Go File Automations where possible.
16. If the Logic Apps workflow needs to manage SFTP To Go configuration, use the Azure Logic Apps HTTP action to call the SFTP To Go REST API. Configure the method, URL, headers, body, and API key according to the SFTP To Go API documentation, and limit API access to the operations the workflow requires.
17. Connect the Logic Apps workflow to the systems that need business context. For example, Azure Logic Apps can route file metadata or file outputs to Azure Storage, Service Bus, Event Grid, Microsoft Teams, Outlook, SharePoint, SQL, Dataverse, ticketing systems, approval steps, validation services, or custom APIs.
18. Make the workflow safe to retry. SFTP To Go webhook and automation delivery can be retried, so use event IDs, delivery IDs, execution IDs, or X-Idempotency-Key values where available to avoid duplicate tickets, duplicate records, repeated approvals, or repeated external actions.
19. Secure the receiving Logic Apps endpoint. Protect the generated Request trigger URL, use HTTPS, validate any configured authorization header, and restrict inbound access where appropriate. If your security model requires SFTP To Go signature validation, validate the X-Hub-Signature header before business actions run, either in the workflow or in a fronting service such as Azure API Management or Azure Functions.
20. Test the complete workflow by uploading, downloading, deleting, or scheduling a test file in SFTP To Go. Confirm that the SFTP To Go event or automation runs, Azure Logic Apps receives the payload, SFTP-SSH or HTTP actions complete as expected, and the target Azure or business systems receive the correct file metadata or file output.
21. Monitor both sides after publishing. In SFTP To Go, review webhook delivery, automation execution history, retries, pauses, and file activity. In Azure Logic Apps, review workflow run history, failed actions, connector connections, trigger activity, retry behavior, and external system responses.
22. As the workflow matures, keep file governance and storage-side file actions inside SFTP To Go where possible, and use Azure Logic Apps for broader coordination across Azure services, Microsoft 365, business apps, approvals, notifications, enrichment, and reporting.

You can find further insight into SFTP webhook notifications, SFTP file automations, SFTP management APIs, Azure Logic Apps Request trigger, Azure Logic Apps SFTP-SSH connector, and Azure Logic Apps HTTP action workflows.