Can Google Cloud Storage and Google Drive talk in both directions?

Yes. Build one flow that starts in Google Cloud Storage 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.

Connect Google Cloud Storage to Google Drive

Move data between Google Cloud Storage 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.

Start building Explore Google Cloud Storage Explore Google Drive

Google Cloud Storage triggers: 2
Google Cloud Storage actions: 12
Google Drive triggers: 3
Google Drive actions: 17

Automation ideas

What you can build with Google Cloud Storage and Google Drive

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

New Object Created in Google Cloud Storage creates Create new folder in Google Drive
Triggers when a new object is created in a bucket
New File in Google Drive creates Create Bucket in Google Cloud Storage
Trigger when a new file is uploaded.
New Object Created in Google Cloud Storage creates Create new file in Google Drive
Triggers when a new object is created in a bucket
New File in Google Drive creates Delete Empty Bucket in Google Cloud Storage
Trigger when a new file is uploaded.
New Object Created in Google Cloud Storage creates Upload file in Google Drive
Triggers when a new object is created in a bucket
New File in Google Drive creates Clone Object in Google Cloud Storage
Trigger when a new file is uploaded.