Can Google Cloud Storage and CloudConvert talk in both directions?

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

Connect Google Cloud Storage to CloudConvert

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

Start building Explore Google Cloud Storage Explore CloudConvert

Google Cloud Storage triggers: 2
Google Cloud Storage actions: 12
CloudConvert triggers: 3
CloudConvert actions: 7

Automation ideas

What you can build with Google Cloud Storage and CloudConvert

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

New Object Created in Google Cloud Storage creates Convert File in CloudConvert
Triggers when a new object is created in a bucket
New Job Event in CloudConvert creates Create Bucket in Google Cloud Storage
Triggers when a new job has been created
New Object Created in Google Cloud Storage creates Capture Website in CloudConvert
Triggers when a new object is created in a bucket
New Job Event in CloudConvert creates Delete Empty Bucket in Google Cloud Storage
Triggers when a new job has been created
New Object Created in Google Cloud Storage creates Merge Files to PDF in CloudConvert
Triggers when a new object is created in a bucket
New Job Event in CloudConvert creates Clone Object in Google Cloud Storage
Triggers when a new job has been created