Can Google Docs and CloudConvert talk in both directions?

Yes. Build one flow that starts in Google Docs 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 Docs to CloudConvert

Move data between Google Docs 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 Docs Explore CloudConvert

Google Docs triggers: 1
Google Docs actions: 6
CloudConvert triggers: 3
CloudConvert actions: 7

Automation ideas

What you can build with Google Docs and CloudConvert

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

New Document in Google Docs creates Convert File in CloudConvert
Triggers when a new document is added to a specific folder(optional).
New Job Event in CloudConvert creates Create Document in Google Docs
Triggers when a new job has been created
New Document in Google Docs creates Capture Website in CloudConvert
Triggers when a new document is added to a specific folder(optional).
New Job Event in CloudConvert creates Edit template file in Google Docs
Triggers when a new job has been created
New Document in Google Docs creates Merge Files to PDF in CloudConvert
Triggers when a new document is added to a specific folder(optional).
New Job Event in CloudConvert creates Read Document in Google Docs
Triggers when a new job has been created