Skip to content
CloudConvert logoGoogle Drive logo

Connect CloudConvert to Google Drive

Move data between CloudConvert and Google Drive 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.

CloudConvert triggers
3
CloudConvert actions
7
Google Drive triggers
3
Google Drive actions
17

Automation ideas

What you can build with CloudConvert and Google Drive

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

  • New Job Event in CloudConvert creates Create new folder in Google Drive

    Triggers when a new job has been created

  • New File in Google Drive creates Convert File in CloudConvert

    Trigger when a new file is uploaded.

  • New Job Event in CloudConvert creates Create new file in Google Drive

    Triggers when a new job has been created

  • New File in Google Drive creates Capture Website in CloudConvert

    Trigger when a new file is uploaded.

  • New Job Event in CloudConvert creates Upload file in Google Drive

    Triggers when a new job has been created

  • New File in Google Drive creates Merge Files to PDF in CloudConvert

    Trigger when a new file is uploaded.

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 CloudConvert and acts in Google Drive, 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.