Skip to content
FTP/SFTP logoGitHub logo

Connect FTP/SFTP to GitHub

Move data between FTP/SFTP and GitHub 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.

FTP/SFTP triggers
1
FTP/SFTP actions
8
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with FTP/SFTP and GitHub

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

  • New File in FTP/SFTP creates Create Issue in GitHub

    Trigger when a new file is created or modified.

  • New Pull Request in GitHub creates Create File from Text in FTP/SFTP

    Triggers when there is activity on a pull request.

  • New File in FTP/SFTP creates Get issue information in GitHub

    Trigger when a new file is created or modified.

  • New Pull Request in GitHub creates Upload File in FTP/SFTP

    Triggers when there is activity on a pull request.

  • New File in FTP/SFTP creates Create comment on a issue in GitHub

    Trigger when a new file is created or modified.

  • New Pull Request in GitHub creates Read File Content in FTP/SFTP

    Triggers when there is activity on a pull request.

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 FTP/SFTP and acts in GitHub, 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.