Can Google Drive and PDF.co talk in both directions?

Yes. Build one flow that starts in Google Drive and acts in PDF.co, 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 Drive to PDF.co

Move data between Google Drive and PDF.co 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 Drive Explore PDF.co

Google Drive triggers: 3
Google Drive actions: 17
PDF.co triggers: 0
PDF.co actions: 34

Automation ideas

What you can build with Google Drive and PDF.co

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

New File in Google Drive creates Add Barcode to PDF in PDF.co
Triggers when a file is created in Drive or the chosen folder. Uploads and copies count. A file moved in from another folder fires only if it is newer than the last file this trigger sent.
New File in Google Drive creates Add Image to PDF in PDF.co
Triggers when a file is created in Drive or the chosen folder. Uploads and copies count. A file moved in from another folder fires only if it is newer than the last file this trigger sent.
New File in Google Drive creates Add Text to PDF in PDF.co
Triggers when a file is created in Drive or the chosen folder. Uploads and copies count. A file moved in from another folder fires only if it is newer than the last file this trigger sent.
New Folder in Google Drive creates Add Barcode to PDF in PDF.co
Triggers when a new folder is created in Drive or the chosen folder.