Can GitLab and FTP/SFTP talk in both directions?

Yes. Build one flow that starts in GitLab 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.

Connect GitLab to FTP/SFTP

Move data between GitLab 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.

Start building Explore GitLab Explore FTP/SFTP

GitLab triggers: 1
GitLab actions: 2
FTP/SFTP triggers: 1
FTP/SFTP actions: 8

Automation ideas

What you can build with GitLab and FTP/SFTP

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

New Project Issue Event in GitLab creates Create File from Text in FTP/SFTP
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New File in FTP/SFTP creates Create Issue in GitLab
Trigger when a new file is created or modified.
New Project Issue Event in GitLab creates Upload File in FTP/SFTP
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New File in FTP/SFTP creates Custom API Call in GitLab
Trigger when a new file is created or modified.
New Project Issue Event in GitLab creates Read File Content in FTP/SFTP
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.