Skip to content
Azure DevOps logoFTP/SFTP logo

Connect Azure DevOps to FTP/SFTP

Move data between Azure DevOps and FTP/SFTP the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Azure DevOps triggers
2
Azure DevOps actions
6
FTP/SFTP triggers
1
FTP/SFTP actions
8

Automation ideas

What you can build with Azure DevOps and FTP/SFTP

A few flows teams run between Azure DevOps and FTP/SFTP. Use one as a starting point, or build your own from scratch.

  • New or Updated Work Item (Instant) in Azure DevOps creates Create File from Text in FTP/SFTP

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New File in FTP/SFTP creates Create Work Item in Azure DevOps

    Trigger when a new file is created or modified.

  • New or Updated Work Item (Instant) in Azure DevOps creates Upload File in FTP/SFTP

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New File in FTP/SFTP creates Get Work Item in Azure DevOps

    Trigger when a new file is created or modified.

  • New or Updated Work Item (Instant) in Azure DevOps creates Read File Content in FTP/SFTP

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New File in FTP/SFTP creates Update Work Item in Azure DevOps

    Trigger when a new file is created or modified.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Azure DevOps and acts in FTP/SFTP, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.