Connect Paige to monday.com
Create a monday.com item for every document Paige finishes — columns filled from Paige's extracted fields and the PDF uploaded to a Files column — with a Zapier Zap or a Make scenario watching Paige's SFTP export folder.
Before you begin
- A monday.com board with columns for the fields you want, including a Files column for the PDF
- 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 an item on a monday.com board within minutes — name and columns filled from Paige's fields, the PDF in a Files column — so the team works the document from the board instead of a shared inbox.
monday.com (monday, monday work management) has no watched folder, so the route is an automation platform: SFTP trigger → keep only the data file → read the values → create the item → upload the PDF to its Files column.
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/intake.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, 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 board
Add a column per Paige field you want on the item (Text, Date, Numbers, Status as fits), plus a Files column named Document. Note the group new items should land in.
Step 3 — Build the automation
Zapier
SFTP by Zapier → New or Updated File (connection: 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,
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;
monday.com → Create Item. Pick the board and group; Item Name from Paige fields (for example the vendor and invoice number); map each column from the Code step. Dates go to Date columns as
YYYY-MM-DD(use Formatter by Zapier if Paige's printed date differs), amounts to Numbers columns without currency symbols.SFTP by Zapier → Download File, path = the folder plus
pdf_file.monday.com → Upload File to Specific Column. Item = the one from step 4; column =
Document; file = the download from step 5.Turn the Zap on.
The finished Zap with the monday.com Create Item step expanded, showing columns mapped from Paige fields
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.
monday.com → Create an Item with the board, group, name, and column values mapped from the parsed fields.
SFTP → Get a file with path = folder plus parsed
metadata.pdf_file, then monday.com → Add a File to a Column (or the equivalent file-upload module) for the item from module 3 and theDocumentcolumn.Set the schedule and turn the scenario on.
Step 4 — Test it
Process one document through the scan job in Paige and wait for the export.
Check the automation's run history: one run, every step green.
Open the board. What you should see: a new item with the columns filled and the PDF in
Document.
When it doesn't work
| Symptom | Where to look |
|---|---|
| The automation never runs | Wrong folder, or a subfolder. |
| Runs four times per document | The .json filter is missing. |
| A column stays empty | Type mismatch — a text date into a Date column, or a Status label that doesn't exist. Convert, or use Text columns. |
| Item created without the file | The item ID from Create Item wasn't passed to the upload step, or the column isn't a Files column. |
| Nothing arrives from Paige | Auto-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.
