Skip to content
Cloudinary logoCloudConvert logo

Connect Cloudinary to CloudConvert

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

Cloudinary triggers
2
Cloudinary actions
5
CloudConvert triggers
3
CloudConvert actions
7

Automation ideas

What you can build with Cloudinary and CloudConvert

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

  • New Resource in Cloudinary creates Convert File in CloudConvert

    Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.

  • New Job Event in CloudConvert creates Upload Resource in Cloudinary

    Triggers when a new job has been created

  • New Resource in Cloudinary creates Capture Website in CloudConvert

    Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.

  • New Job Event in CloudConvert creates Delete Resource in Cloudinary

    Triggers when a new job has been created

  • New Resource in Cloudinary creates Merge Files to PDF in CloudConvert

    Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.

  • New Job Event in CloudConvert creates Create Usage Report in Cloudinary

    Triggers when a new job has been created

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 Cloudinary 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.