Can FTP/SFTP and CloudConvert talk in both directions?

Yes. Build one flow that starts in FTP/SFTP and acts in CloudConvert, 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 FTP/SFTP to CloudConvert

Move data between FTP/SFTP and CloudConvert 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 FTP/SFTP Explore CloudConvert

FTP/SFTP triggers: 1
FTP/SFTP actions: 8
CloudConvert triggers: 3
CloudConvert actions: 7

Automation ideas

What you can build with FTP/SFTP and CloudConvert

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

New File in FTP/SFTP creates Convert File in CloudConvert
Trigger when a new file is created or modified.
New Job Event in CloudConvert creates Create File from Text in FTP/SFTP
Triggers when a new job has been created
New File in FTP/SFTP creates Capture Website in CloudConvert
Trigger when a new file is created or modified.
New Job Event in CloudConvert creates Upload File in FTP/SFTP
Triggers when a new job has been created
New File in FTP/SFTP creates Merge Files to PDF in CloudConvert
Trigger when a new file is created or modified.
New Job Event in CloudConvert creates Read File Content in FTP/SFTP
Triggers when a new job has been created