Can Cloudinary and Google Cloud Storage talk in both directions?

Yes. Build one flow that starts in Cloudinary and acts in Google Cloud Storage, 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 Cloudinary to Google Cloud Storage

Move data between Cloudinary and Google Cloud Storage 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 Cloudinary Explore Google Cloud Storage

Cloudinary triggers: 2
Cloudinary actions: 5
Google Cloud Storage triggers: 2
Google Cloud Storage actions: 12

Automation ideas

What you can build with Cloudinary and Google Cloud Storage

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

New Resource in Cloudinary creates Create Bucket in Google Cloud Storage
Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.
New Object Created in Google Cloud Storage creates Upload Resource in Cloudinary
Triggers when a new object is created in a bucket
New Resource in Cloudinary creates Delete Empty Bucket in Google Cloud Storage
Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.
New Object Created in Google Cloud Storage creates Delete Resource in Cloudinary
Triggers when a new object is created in a bucket
New Resource in Cloudinary creates Clone Object in Google Cloud Storage
Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.
New Object Created in Google Cloud Storage creates Create Usage Report in Cloudinary
Triggers when a new object is created in a bucket