AdemeroHelp

Connect Paige to Notion

Add a row to a Notion database for every document Paige finishes — properties filled from Paige's extracted fields, the PDF uploaded to a Files property — with a Zapier Zap or a Make scenario watching Paige's SFTP export folder.

For everyone45 minutesVerified 2026-09-05

Before you begin

  • A Notion database with properties for the fields you want, including a Files & media property for the PDF, shared with the integration
  • A paid Zapier or Make plan that includes the SFTP connector
  • 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 becomes a row in a Notion database within minutes — properties filled from Paige's fields, the PDF in a Files property — so a contract tracker, vendor log, or intake register fills itself.

Notion has no watched folder, so the route is an automation platform: SFTP trigger → keep only the data file → read the values → create the database item → upload the PDF to its Files property.

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/contracts.

  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, pick the document type under Document Types, set Auto Field Entry Complete to Yes, and decide whether to require Human Reviewed = Reviewed. Click Save.

Open port 22 on your firewall to Paige's address ranges — Outbound IP ranges for firewall allow-lists.

Step 2 — Prepare the database

Add a property per Paige field (Text, Date, Number, Select as fits), plus a Files & media property named Document. Share the database with the Zapier or Make integration (… > Connections on the database page) or the automation can't see it.

Step 3 — Build the automation

Zapier

  1. 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, 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. Notion → Create Data Source Item. Pick the database; set the title property from Paige fields (for example the counterparty and document number); map the other properties from the Code step. Dates go to Date properties as YYYY-MM-DD (use Formatter by Zapier if Paige's printed date differs); numbers without currency symbols.

  2. SFTP by Zapier → Download File, path = the folder plus pdf_file.

  3. Notion → Upload File to Data Source Item. Item = the one from step 4; property = Document; file = the download from step 5.

  4. Turn the Zap on.

Make

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

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

  3. Notion → Create a Database Item with the properties mapped from the parsed fields.

  4. SFTP → Get a file with path = folder plus parsed metadata.pdf_file, then the Notion module that uploads a file to the item's Files property (or, if your Make plan's Notion app lacks one, put the PDF in a cloud drive with one of the storage guides and store its link in a URL property).

  5. Set the schedule and turn the scenario on.

Step 4 — Test it

  1. Process one document through the scan job in Paige and wait for the export.

  2. Check the automation's run history: one run, every step green.

  3. Open the database. What you should see: a new row with the properties filled and the PDF in Document.

When it doesn't work

SymptomWhere to look
The automation can't see the databaseIt isn't shared with the integration. Add the connection on the database page.
The automation never runsWrong folder, or a subfolder.
Runs four times per documentThe .json filter is missing.
A property stays emptyType mismatch — a text date into a Date property, or a Select option that doesn't exist. Convert, or use Text.
Row created without the fileThe item ID from the create step wasn't passed to the upload step, or the property isn't Files & media.
Nothing arrives from PaigeAuto-export criteria aren't met, or the document was processed before you enabled auto export. Export 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.