Connect Paige to Google Drive
Two working paths from Paige into Google Drive: Drive for desktop syncing a folder that Paige's export writes into, or an automation on Zapier, Make, or Power Automate that uploads each finished document with a name built from its contents. Which to pick and the step-by-step guides.
Every document Paige finishes can land in Google Drive as a searchable PDF — in My Drive or a shared drive — with no one uploading anything. Use Drive for desktop and a folder, or an automation that also names each file from its own contents.
Google Drive (Drive, Google Workspace Drive, "GDrive") has no folder-watching import of its own, so Paige reaches it in one of two ways.
What lands in Google Drive
| Synced-folder path | Automation path | |
|---|---|---|
| The searchable PDF | In the synced folder, with Paige's generated filename | In the folder you choose, named from Paige's fields (for example INV-20441 – Acme Office Supply.pdf) |
Paige's data files (.json, .xml, .csv) | Land alongside the PDF | Not uploaded unless you want them |
| Where it runs | On a PC that stays on and signed in | In the cloud; nothing on-premises |
| Shared drives | Drive for desktop syncs computer folders into Computers, not into shared drives; move files with a Drive rule or by hand | Upload straight into a shared drive folder |
Drive's search indexes the PDF text either way, so documents are findable by their contents from day one.
Pick a path
| Path | Choose it when | Guide |
|---|---|---|
| Synced folder | You have a PC that stays on, you're fine with Paige's filenames, and you don't want another subscription | Export Paige documents to a synced Google Drive folder |
| Automation (Zapier, Make, or Power Automate) | You want files named from their contents, delivered into a shared drive, with nothing running on a PC | Send Paige documents to Google Drive with an automation |