Can Box and CloudConvert talk in both directions?

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

Move data between Box 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 Box Explore CloudConvert

Box triggers: 3
Box actions: 1
CloudConvert triggers: 3
CloudConvert actions: 7

Automation ideas

What you can build with Box and CloudConvert

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

New File in Box creates Convert File in CloudConvert
Triggers when a file is uploaded
New Job Event in CloudConvert creates Custom API Call in Box
Triggers when a new job has been created
New File in Box creates Capture Website in CloudConvert
Triggers when a file is uploaded
Job Finished in CloudConvert creates Custom API Call in Box
Triggers when a CloudConvert job has been completed
New File in Box creates Merge Files to PDF in CloudConvert
Triggers when a file is uploaded
Job Failed in CloudConvert creates Custom API Call in Box
Triggers when a CloudConvert job has failed