Send Paige documents to Google Drive with an automation
Build the Zapier Zap, Make scenario, or Power Automate flow that watches Paige's SFTP export folder and uploads each finished document to a Google Drive or shared drive folder, named from the document's own contents.
Before you begin
- A Google account with edit rights on the destination folder (My Drive or a shared drive)
- An account on Zapier, Make, or Power Automate that includes the SFTP connector (a paid tier on all three)
- An SFTP server Paige can reach, with a folder for this scan job
- A Paige scan job with document types and fields set up
At the end of this guide, every document Paige finishes is uploaded to the Google Drive folder you choose — including a shared drive — within minutes, as a searchable PDF named from its own contents, with nothing running on a PC.
The shape is the same on every platform: watch the SFTP folder → keep only the data file → read the values → fetch the PDF → upload it with a good name. Paige uploads the PDF before the data file, so the PDF is always there when the automation fires.
Step 1 — Point Paige at your SFTP server
In Paige, open Settings (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose Export.
Click the FTP card. Enter the FTP Address, Port
22, Username, Password, and in FTP Folder Path a folder for this scan job, such as/paige/invoices.Click Test Connection. What you should see:
FTP connection successful!Connect —Connected to FTP Server!and a green Connected label.Turn on Enable Auto Export. Under Auto Export Settings, switch on Only documents having a document type, set Auto Field Entry Complete to Yes (the file name needs the values), and set Human Reviewed to Reviewed if a person checks documents in Paige first. Click Save.
Open port 22 on your firewall to Paige's address ranges — Outbound IP ranges for firewall allow-lists.
Step 2 — Build the automation
Zapier
Trigger: SFTP by Zapier → New or Updated File, connected with Host, Username, Port Number 22, Password; folder = the scan job's folder.
Filter by Zapier: File Name (Text) Ends with
.json.Code by Zapier → Run Javascript, with
filemapped to the trigger's file:const doc = await (await fetch(inputData.file)).json(); const out = { pdf_file: doc.metadata.pdf_file, document_type: doc.metadata.document_type }; for (const [k, v] of Object.entries(doc.fields)) out[k] = v; return out;
SFTP by Zapier → Download File, path = the folder plus
pdf_filefrom step 3.Google Drive → Upload File. Choose the Drive (My Drive or a shared drive) and Folder; set File to the Download File step's output; set the file name from step 3's fields, for example
{{Invoice Number}} - {{Vendor Name}}, with the extensionpdf.Turn the Zap on. Zapier polls the folder on your plan's interval (1–15 minutes).
Make
SFTP → Watch files in a folder (connection: Host, Port 22, Auth Type Username and Password), pointed at the scan job's folder.
Filter: File name Ends with
.json.SFTP → Get a file, then JSON → Parse JSON on its data. Run once with a real file so Make learns the fields.
SFTP → Get a file with path = folder plus parsed
metadata.pdf_file.Google Drive → Upload a File. Pick the drive and folder, map the file data from module 4, and set the file name from the parsed fields, ending in
.pdf.Set the schedule and turn the scenario on.
Power Automate
SFTP - SSH: When a file is added or modified (connection: Host server address, User name, Password, Port number 22), folder = the scan job's folder, Include file content on.
Condition: File name ends with
.json; the rest goes in If yes.Parse JSON on the trigger's File content, schema generated from a real
.json.SFTP - SSH → Get file content using path, path = folder plus the parsed
pdf_file.Google Drive → Create file (V2). Pick the Folder, set File name from the parsed fields ending in
.pdf, and File content from step 4.Save.
Power Automate's Google Drive connector caps content at 10 MB per file. Long scanned documents exceed that; use Zapier or Make for those, or the synced-folder path.
Step 3 — Test it
Process one document through the scan job (review it if you required review) and wait for the export.
Check the automation's run history: one run, triggered by the
.jsonfile.Open the Drive folder. What you should see: the PDF with the name you built. Search Drive for a word from the document — it's found.
When it doesn't work
| Symptom | Where to look |
|---|---|
| The automation never runs | Wrong folder, or a subfolder (none of the three triggers watch subfolders). |
| Runs four times per document | The .json filter is missing. |
| Upload fails with a size error | Power Automate's 10 MB cap. Switch platforms or paths. |
| The name is blank or wrong | The parse step was built from a sample missing that field, or the field is empty on that document. Add a fallback to pdf_file. |
| Nothing arrives from Paige | Auto-export criteria aren't met, or the document was processed before you enabled auto export. Export it once from the Documents page with Export and tick FTP. |
If the Paige side is the problem, contact Ademero support with the scan job name and the message from Test Connection.
