Skip to content
Netlify logoCloudConvert logo

Connect Netlify to CloudConvert

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

Netlify triggers
4
Netlify actions
4
CloudConvert triggers
3
CloudConvert actions
7

Automation ideas

What you can build with Netlify and CloudConvert

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

  • New Deploy Started in Netlify creates Convert File in CloudConvert

    Fires immediately when a deploy job starts on your Netlify site.

  • New Job Event in CloudConvert creates Start Deploy in Netlify

    Triggers when a new job has been created

  • New Deploy Started in Netlify creates Capture Website in CloudConvert

    Fires immediately when a deploy job starts on your Netlify site.

  • New Job Event in CloudConvert creates Get Site in Netlify

    Triggers when a new job has been created

  • New Deploy Started in Netlify creates Merge Files to PDF in CloudConvert

    Fires immediately when a deploy job starts on your Netlify site.

  • New Job Event in CloudConvert creates List Site Deploys in Netlify

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