AdemeroHelp

Send Paige documents to Box 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 Box folder, named from the document's own contents — and, on Zapier, fills a Box metadata template from Paige's fields.

Administrators45 minutesVerified 2026-09-05

Before you begin

  • A Box account with upload rights on the destination folder
  • 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 Box folder you choose within minutes, as a searchable PDF named from its own contents, with nothing running on a PC — and if you use Box metadata templates, the Zapier version fills them from Paige's fields.

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

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

  2. 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.

  3. Click Test Connection. What you should see: FTP connection successful! Connect — Connected to FTP Server! and a green Connected label.

  4. Turn on Enable Auto Export. Under Auto Export Settings, switch on Only documents having a document type, set Auto Field Entry Complete to Yes, 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

  1. Trigger: SFTP by Zapier → New or Updated File (connection: Host, Username, Port Number 22, Password), folder = the scan job's folder.

  2. Filter by Zapier: File Name (Text) Ends with .json.

  3. Code by Zapier → Run Javascript, with file mapped 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;

  1. SFTP by Zapier → Download File, path = folder plus pdf_file from step 3.

  2. Box → Upload File. Choose the Folder, set the file to the Download File output, and set the file name from step 3's fields — {{Invoice Number}} - {{Vendor Name}} — with extension pdf.

  3. Optional — Box → Add Metadata to File. Pick the file from step 5 and the metadata template, then map each template field to a Paige field from step 3. Box metadata is what powers Box's filtered views and reports.

  4. Turn the Zap on. Zapier polls on your plan's interval (1–15 minutes).

Make

  1. SFTP → Watch files in a folder (connection: Host, Port 22, Auth Type Username and Password), pointed at the scan job's folder.

  2. Filter: File name Ends with .json.

  3. SFTP → Get a file, then JSON → Parse JSON on its data. Run once with a real file so Make learns the fields.

  4. SFTP → Get a file with path = folder plus parsed metadata.pdf_file.

  5. Box → Upload a File. Pick the folder, map the file data from module 4, and set the file name from the parsed fields, ending in .pdf.

  6. Set the schedule and turn the scenario on.

Power Automate

  1. 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.

  2. Condition: File name ends with .json; the rest goes in If yes.

  3. Parse JSON on the trigger's File content, schema generated from a real .json.

  4. SFTP - SSH → Get file content using path, path = folder plus the parsed pdf_file.

  5. Box → Create file. Folder Path = the destination (write it as /Finance/Paige Invoices, not the //All Files/… form the picker produces), File Name from the parsed fields ending in .pdf, File Content from step 4.

  6. Save.

Important

Power Automate's Box connector caps files at 75 MB and doesn't support single-sign-on connections — connect with a standard Box login.

Step 3 — Test it

  1. Process one document through the scan job (review it if you required review) and wait for the export.

  2. Check the automation's run history: one run, triggered by the .json file.

  3. Open the Box folder. What you should see: the PDF with the name you built and, if you added it, the metadata filled. Search Box for a word from the document — it's found.

When it doesn't work

SymptomWhere to look
The automation never runsWrong folder, or a subfolder (none of the three triggers watch subfolders).
Runs four times per documentThe .json filter is missing.
Power Automate Create file times outA stray character in the path or name; check the //All Files note above.
Metadata step failsA template field received text of the wrong type (a text date into a date field). Convert in a Formatter step first.
The name is blank or wrongThe 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 PaigeAuto-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.