Connect Paige to any app with Zapier, Make, or Power Automate

How the handoff works

1. 1

   A document finishes in Paige (separated, typed, fields extracted, optionally reviewed).

2. 2

   Paige uploads the document to your SFTP folder as a PDF, then uploads three small data files with the same base name.

3. 3

   Your Zap, scenario, or flow notices the new data file, reads the field values out of it, fetches the PDF, and creates the record in the target app.

Step 1: Point Paige at your SFTP server

1. 1

   Open Settings (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose Export.

2. 2

   Click the FTP card.

3. 3

   Enter the server's FTP Address and Port (SFTP servers use 22), then the Username and Password Paige should sign in with.

4. 4

   In FTP Folder Path, enter the folder Paige should write into, such as /paige/invoices. Paige creates it if it doesn't exist. Give each scan job its own folder — it keeps the automations simple.

5. 5

   Click Test Connection.

   What you should see: FTP connection successful! If you get FTP connection failed: followed by a reason, the reason is the server's own message — a wrong password, a blocked port, or a folder the account can't write to.

6. 6

   Connect. What you should see: Connected to FTP Server! and a green Connected label on the FTP card.

7. 7

   Back on the Export page, turn on Enable Auto Export and set the criteria under Auto Export Settings:

   Setting	Recommendation for an integration
   Document Types	Leave empty for all, or pick only the types the target app should receive
   Only documents having a document type	On — untyped documents rarely map cleanly
   Human Reviewed	Reviewed if a person checks documents in Paige before they go out; All if the automation is the review
   Auto Field Entry Complete	Yes — a document with no field values has nothing to put in the record

   Click Save.

Step 2: Build the automation

Zapier

1. 1

   Trigger: app SFTP by Zapier, event New or Updated File. Create the connection with your Host, Username, Port Number (22), and Password. Set the folder to the path you gave Paige.

2. 2

   Filter: add Filter by Zapier with the rule File Name (Text) Ends with .json. Without this the Zap fires four times per document.

3. 3

   Read the values: add Code by Zapier, event Run Javascript. In Input Data, map file to the trigger's file. Paste:

   const res = await fetch(inputData.file);
   const doc = await res.json();
   const out = { pdf_file: doc.metadata.pdf_file, document_type: doc.metadata.document_type };
   for (const [name, value] of Object.entries(doc.fields)) out[name] = value;
   return out;
   

   Test the step. What you should see: one output field per Paige field, named exactly as the field is named in the scan job, plus pdf_file and document_type.

4. 4

   Fetch the PDF: add SFTP by Zapier, action Download File, and set the path to the folder plus pdf_file from the Code step.

5. 5

   Create the record: add your target app's action — for example QuickBooks Online → Create Bill, Google Drive → Upload File, monday.com → Create Item — and map the Code step's fields into it. Where the action takes a file, map the Download File step's output.

6. 6

   Turn the Zap on.

Make

1. 1

   Trigger: module SFTP → Watch files in a folder. Create the connection with Host, Port (22), Auth Type Username and Password. Point it at the Paige folder.

2. 2

   Filter: on the line after the trigger, add a filter: File name Ends with .json.

3. 3

   Read the values: add SFTP → Get a file for the triggered file, then JSON → Parse JSON with the file's data as its input. Make builds the data structure from a sample the first time you run it — run the scenario once with a real Paige file so the field names appear.

4. 4

   Fetch the PDF: add SFTP → Get a file with the path set to the folder plus the parsed metadata.pdf_file.

5. 5

   Create the record: add the target app's module and map the parsed fields and the PDF file data into it.

6. 6

   Set the schedule (Make runs scenarios every 15 minutes on the basic plan; you can shorten it) and turn the scenario on.

Power Automate

1. 1

   Trigger: connector SFTP - SSH, trigger When a file is added or modified. Create the connection with Host server address, User name, Password, and Port number 22. Under Folder, choose the Paige folder. Leave Include file content on.

2. 2

   Condition: add a Condition: File name ends with .json. Put the rest of the flow in the If yes branch.

3. 3

   Read the values: add Parse JSON. Content is the trigger's File content. For the schema, click Use sample payload to generate schema and paste a real .json from your folder. Every Paige field becomes a token you can pick in later steps.

4. 4

   Fetch the PDF: add SFTP - SSH → Get file content using path, with the path set to the folder plus the parsed pdf_file.

5. 5

   Create the record: add the target connector's action — SharePoint → Create file, Dynamics 365 Business Central → Create record, OneDrive for Business → Create file, and so on — mapping the parsed tokens and the file content.

6. 6

   Save. What you should see: the flow's checker reports no errors, and the first run appears in the run history within a few minutes of Paige exporting a document.

What the JSON looks like

{
  "metadata": {
    "pdf_file": "scan_job_abc123_page_def456_20260905_141502.pdf",
    "scan_job_id": "abc123",
    "page_id": "def456",
    "export_timestamp": "2026-09-05T14:15:02.101234",
    "document_type": "Vendor Invoice"
  },
  "fields": {
    "Vendor Name": "Acme Office Supply",
    "Invoice Number": "INV-20441",
    "Invoice Date": "08/28/2026",
    "Total": "1,284.50"
  },
  "line_items": {
    "fld_lineitems": {
      "name": "Line Items",
      "columns": ["Description", "Qty", "Amount"],
      "rows": {
        "0": { "0": "Copy paper, case", "1": "10", "2": "449.00" },
        "1": { "0": "Toner, black", "1": "5", "2": "835.50" }
      }
    }
  }
}

Test it end to end

1. 1

   In Paige, scan or upload one document into the scan job and let it finish processing. If your auto-export criteria require review, review it.

2. 2

   Watch the SFTP folder: the PDF appears, then the three data files.

3. 3

   Watch the automation's run history: one run, triggered by the .json.

4. 4

   Open the target app: the record exists, its fields match what Paige extracted, and the PDF is attached or filed.

When it doesn't work