Skip to content
Cloudinary logoGoogle Drive logo

Connect Cloudinary to Google Drive

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

Cloudinary triggers
2
Cloudinary actions
5
Google Drive triggers
3
Google Drive actions
17

Automation ideas

What you can build with Cloudinary and Google Drive

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

  • New Resource in Cloudinary creates Create Folder in Google Drive

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

  • New File in Google Drive creates Upload Resource in Cloudinary

    Triggers when a new file is added to Drive or the chosen folder.

  • New Resource in Cloudinary creates Create File from Text in Google Drive

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

  • New File in Google Drive creates Delete Resource in Cloudinary

    Triggers when a new file is added to Drive or the chosen folder.

  • New Resource in Cloudinary creates Upload File in Google Drive

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

  • New File in Google Drive creates Create Usage Report in Cloudinary

    Triggers when a new file is added to Drive or the chosen folder.

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