Azure Logic Apps

Laura-ann Burgess -

SFTP To Go

SFTP To Go gives Azure Logic Apps a controlled file-transfer workspace with standard access methods, event callbacks, in-app file handling, scoped credentials, and audit history.

  • SFTP, FTPS, HTTPS, and S3 endpoints for workflow handoffs
  • Webhooks and File Automations for event-led file handling
  • Folder permissions, API controls, and activity records

Azure Logic Apps

Azure Logic Apps builds workflows across Azure services, Microsoft tools, SaaS apps, data systems, and APIs. With SFTP To Go, Logic Apps can receive file-event requests, work with files through SFTP-SSH, and call management APIs when workflow logic requires it.

  • Start workflows from SFTP To Go events or completed File Automations
  • Use Request, SFTP-SSH, and HTTP actions where they fit
  • Send file context to queues, storage, Microsoft 365, approvals, alerts, or APIs

How does it work?

  1. Start with the workflow shape. Use SFTP To Go webhooks for file-event notifications, File Automations when SFTP To Go should prepare the file first, the SFTP-SSH connector when Logic Apps needs direct file access, and the HTTP action when Logic Apps needs to call the SFTP To Go REST API.
  2. In Azure Logic Apps, create or open the workflow that should receive the file event. For an event-driven build, add the Request trigger named When a HTTP request is received.
  3. Set the Request trigger method to POST. Add a request body JSON schema if you want Logic Apps to expose SFTP To Go payload values as dynamic workflow fields.
  4. Save the workflow, then copy the generated HTTP URL. Azure Logic Apps shows this callback URL only after the workflow has been saved, and SFTP To Go will use it as the delivery endpoint.
  5. In SFTP To Go, create either a webhook notification for upload, download, or delete events, or a File Automation that ends with a webhook request to the Logic Apps URL.
  6. Keep the SFTP To Go trigger focused. Filter by path, actor type, actor ID, or file pattern, and exclude folder events when the workflow should only handle files.
  7. Use SFTP To Go File Automations for file-side work before Azure Logic Apps takes over. Common steps include copy, move, delete, PGP encrypt, PGP decrypt, delay, notifications, and webhook requests.
  8. Test the trigger with a sample upload, download, deletion, or scheduled run in SFTP To Go. Confirm that the Logic Apps run starts and receives the expected payload.
  9. In Azure Logic Apps, inspect the request body. Use fields such as Topic, Data.Path, Data.Size, Actor, Metadata, and automation or idempotency values where available.
  10. Route the workflow according to the event. For example, send file.created to validation or processing, file.downloaded to audit notifications, and file.deleted to record updates or review steps.
  11. When Logic Apps needs the file itself, create an SFTP-SSH connection to SFTP To Go. Use a dedicated SFTP To Go credential, the correct host and port, and the narrowest folder access that supports the workflow.
  12. Add the SFTP-SSH action that matches the task, such as getting file content by path, creating a file, copying a file, deleting a file, listing a folder, or reading file metadata. Use the payload path when the workflow needs to act on the triggering file.
  13. If Logic Apps writes a result file back to SFTP To Go, place it in the correct SFTP path. Use SFTP To Go File Automations for any follow-up file handling such as move, copy, delete, encrypt, decrypt, notify, or webhook request.
  14. Secure and monitor the workflow. Protect the Request trigger URL, use HTTPS, apply authorization or network restrictions where appropriate, validate signatures where required, and review SFTP To Go webhook deliveries and audit logs alongside Azure Logic Apps run history and failed actions.

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.