Can Google Docs and PDFMonkey talk in both directions?

Yes. Build one flow that starts in Google Docs and acts in PDFMonkey, 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 PDFMonkey

Move data between Google Docs and PDFMonkey 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 PDFMonkey

Google Docs triggers: 1
Google Docs actions: 6
PDFMonkey triggers: 1
PDFMonkey actions: 4

Automation ideas

What you can build with Google Docs and PDFMonkey

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

New Document in Google Docs creates Generate Document in PDFMonkey
Triggers when a new document is created in Drive or a chosen folder.
Document Generated in PDFMonkey creates Create Document in Google Docs
Triggers when a document generation completes successfully.
New Document in Google Docs creates Delete Document in PDFMonkey
Triggers when a new document is created in Drive or a chosen folder.
Document Generated in PDFMonkey creates Edit Template File in Google Docs
Triggers when a document generation completes successfully.
New Document in Google Docs creates Find Document in PDFMonkey
Triggers when a new document is created in Drive or a chosen folder.
Document Generated in PDFMonkey creates Read Document in Google Docs
Triggers when a document generation completes successfully.