Integrations
Getting Paige's documents and data into the systems you already run — by export or by API.
Acumatica3 guides
Connect Paige to Acumatica
Two working paths from Paige into Acumatica: an import scenario that loads a batch of AP bills from Paige's CSV, or an integration with Acumatica's REST API that creates each bill and attaches the PDF. Which to pick, what lands in Acumatica, and the step-by-step guides.
Import Paige invoices into Acumatica with an import scenario
Set up an Acumatica CSV data provider and import scenario once, then load each batch of invoices Paige read into Bills and Adjustments with Prepare and Import — vendor, dates, vendor reference, account, and amount filled from Paige's CSV.
Integrate Paige with the Acumatica REST API
For developers: the calls that turn a Paige invoice into an Acumatica AP bill with the PDF attached — sign in, PUT the Bill entity, then upload the file through the bill's files link — fed from Paige's SFTP export files or the Paige API.
Box3 guides
Connect Paige to Box
Two working paths from Paige into Box: Box Drive on a PC exposing a Box folder that Paige's export writes into, or an automation on Zapier, Make, or Power Automate that uploads each finished document with a name built from its contents. Which to pick and the step-by-step guides.
Export Paige documents to a Box Drive folder
Run an SFTP server on a PC that has Box Drive, point Paige at a folder inside Box, and every finished document uploads itself — PDFs plus Paige's data files, nothing to build and no automation subscription.
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.
DocuWare3 guides
Connect Paige to DocuWare
Two working paths from Paige into DocuWare Cloud: Power Automate or Make picks up each finished document from Paige's SFTP export and stores it in a file cabinet with its index fields already filled, using DocuWare's own connectors. Which to pick, what lands in DocuWare, and links to the step-by-step guides.
Send Paige documents to DocuWare with Make
Build the Make scenario that watches Paige's SFTP export folder, parses each document's field values, and stores the PDF in a DocuWare Cloud file cabinet with its index fields filled — using DocuWare's own Make connector.
Send Paige documents to DocuWare with Power Automate
Build the Power Automate flow that watches Paige's SFTP export folder, reads each document's field values, and stores the PDF in a DocuWare Cloud file cabinet with its index fields filled — using DocuWare's own connector.
Dropbox3 guides
Connect Paige to Dropbox
Two working paths from Paige into Dropbox: the Dropbox desktop app syncing a folder that Paige's export writes into, or an automation on Zapier, Make, or Power Automate that uploads each finished document with a name built from its contents. Which to pick and the step-by-step guides.
Export Paige documents to a synced Dropbox folder
Run an SFTP server on a PC that has the Dropbox desktop app, point Paige at a folder inside Dropbox, and every finished document uploads itself — PDFs plus Paige's data files, nothing to build and no automation subscription.
Send Paige documents to Dropbox 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 Dropbox folder, named from the document's own contents.
Dynamics 365 Business Central3 guides
Connect Paige to Dynamics 365 Business Central
Two working paths from Paige into Business Central: a Power Automate flow that creates each purchase invoice from Paige's extracted fields and attaches the PDF using Microsoft's own connector, or a direct integration with the Business Central API for developers. Which to pick, what lands in Business Central, and the step-by-step guides.
Create Business Central purchase invoices from Paige with Power Automate
Build the Power Automate flow that watches Paige's SFTP export folder, reads each invoice's field values, creates a draft purchase invoice in Dynamics 365 Business Central with a line at the total, and attaches the PDF — all with Microsoft's Business Central connector.
Integrate Paige with the Business Central API
For developers: the four Business Central API calls that turn a Paige invoice into a draft purchase invoice with the PDF attached — create the invoice, add lines, create the attachment record, upload its content — fed either from Paige's SFTP export files or straight from the Paige API.
Google Drive3 guides
Connect Paige to Google Drive
Two working paths from Paige into Google Drive: Drive for desktop syncing a folder that Paige's export writes into, or an automation on Zapier, Make, or Power Automate that uploads each finished document with a name built from its contents. Which to pick and the step-by-step guides.
Export Paige documents to a synced Google Drive folder
Run an SFTP server on a PC that has Drive for desktop, sync the Paige export folder to Google Drive, and every finished document uploads itself — PDFs plus Paige's data files, nothing to build and no automation subscription.
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.
HubSpot3 guides
Connect Paige to HubSpot
Two working paths from Paige into HubSpot: a Zapier automation that uploads each document's PDF to HubSpot Files and logs it on the matching contact, company, or deal with Paige's extracted details, or HubSpot's import tool for batches of records from Paige's CSV. Which to pick and the step-by-step guides.
Import Paige documents into HubSpot from CSV
Export a batch of documents from Paige and load the one-row-per-document CSV with HubSpot's import tool — contacts, companies, deals, or custom objects created or updated from Paige's fields, mapped column by column, no subscription.
Send Paige documents to HubSpot with Zapier
Build the Zap that watches Paige's SFTP export folder, finds the HubSpot contact or company, uploads the PDF to HubSpot Files, and logs a note on the record with Paige's extracted details and the file attached.
Laserfiche3 guides
Connect Paige to Laserfiche
Two working paths from Paige into Laserfiche: a Power Automate flow that imports each finished document through the Laserfiche API with its template and fields filled from Paige's extracted values, or Import Agent watching a folder that Paige's export writes into. Which to pick, what lands in the repository, and the step-by-step guides.
Export Paige documents to Laserfiche with Import Agent
Point Paige's SFTP export at a folder that Laserfiche Import Agent watches, and every finished document is filed into the repository with a template and tags assigned — for self-hosted Laserfiche or Laserfiche Cloud, with no automation platform. Paige's per-document field values stay in its data files for Laserfiche to fill in its own way.
Send Paige documents to Laserfiche with Power Automate
Build the Power Automate flow that watches Paige's SFTP export folder, reads each document's field values, and imports the PDF into Laserfiche Cloud through the Laserfiche API with its template assigned and fields filled — using a service principal, exactly as Laserfiche's own low-code guide describes.
NetSuite4 guides
Connect Paige to NetSuite
Three working paths from Paige into NetSuite: a SuiteScript that pulls each finished invoice from Paige's SFTP export and creates the vendor bill with the PDF attached; NetSuite's CSV Import Assistant for batches from Paige's CSV; or emailing Paige's PDFs to NetSuite Bill Capture. Which to pick, what lands in NetSuite, and the step-by-step guides.
Create NetSuite vendor bills from Paige with SuiteScript
A scheduled SuiteScript uses NetSuite's built-in N/sftp module to pull each finished invoice from Paige's SFTP export folder, creates the vendor bill from Paige's field values, and attaches the PDF from the File Cabinet — no middleware, NetSuite pulls directly.
Email Paige invoices to NetSuite Bill Capture
The lowest-effort route into NetSuite: a one-step automation emails each PDF Paige finishes to your NetSuite Bill Capture address, and the invoice appears on the Scanned Vendor Bills page for review. Paige's own field values aren't sent — just the clean, separated, searchable PDF.
Import Paige invoices into NetSuite with the CSV Import Assistant
Export a batch of invoices from Paige, shape the one-row-per-document CSV into NetSuite's vendor bill import layout, and load it with the CSV Import Assistant — vendor, date, reference, and expense lines filled from Paige, PDFs attached by hand if you want them.
OneDrive3 guides
Connect Paige to OneDrive
Two working paths from Paige into OneDrive for Business: a Power Automate flow that files each finished document into a OneDrive folder with a meaningful name, or the OneDrive sync app on a PC so Paige's export lands in OneDrive directly. Which to pick and the step-by-step guides.
Export Paige documents to a synced OneDrive folder
The no-license path: run an SFTP server on a PC that syncs OneDrive, point Paige at a folder inside OneDrive, and every finished document uploads itself — PDFs plus Paige's data files, nothing to build.
Send Paige documents to OneDrive with Power Automate
Build the Power Automate flow that watches Paige's SFTP export folder, reads each document's field values, and creates the PDF in a OneDrive for Business folder with a name built from the document's own contents.
QuickBooks Online3 guides
Connect Paige to QuickBooks Online
Two working paths from Paige into QuickBooks Online: an automation on Zapier or Make that creates each bill and attaches the PDF as soon as Paige finishes the invoice, or QuickBooks' own bill import that loads a batch of bills from Paige's CSV. Which to pick, what lands in QuickBooks, and the step-by-step guides.
Import Paige invoices into QuickBooks Online from CSV
Export a batch of invoices from Paige, open the one-row-per-document CSV, and load it with QuickBooks Online's own bill importer — mapping Paige's columns to vendor, dates, bill number, account, and amount. No automation platform, no subscription; PDFs are attached by hand if you want them.
Send Paige invoices to QuickBooks Online with Zapier or Make
Build the Zap or Make scenario that watches Paige's SFTP export folder, finds or creates the vendor, creates the bill in QuickBooks Online from Paige's extracted fields, and attaches the PDF — so every invoice Paige finishes becomes a bill on its own.
Sage Intacct3 guides
Connect Paige to Sage Intacct
Two working paths from Paige into Sage Intacct: Intacct's own CSV bill import for batches from Paige's CSV, or an integration with the Intacct API that creates each bill with the PDF attached as its supporting document. Which to pick, what lands in Intacct, and the step-by-step guides.
Import Paige invoices into Sage Intacct from CSV
Export a batch of invoices from Paige, copy the one-row-per-document CSV into Intacct's bill import template, and load it from Accounts Payable > Bills > Import — bills with vendor, dates, bill number, account, and amount filled from Paige; PDFs attached by hand if you want them.
Integrate Paige with the Sage Intacct API
For developers: the two Intacct Web Services calls that turn a Paige invoice into an AP bill with the PDF attached — create the supporting document, then create the bill referencing it — fed from Paige's SFTP export files or the Paige API.
Salesforce3 guides
Connect Paige to Salesforce
Two working paths from Paige into Salesforce: an automation on Zapier or Make that creates a record from each document's fields and attaches the PDF as a Salesforce File, or Data Loader for batches — records from Paige's CSV, files from Paige's PDFs. Which to pick, what lands in Salesforce, and the step-by-step guides.
Load Paige documents into Salesforce with Data Loader
Two Data Loader runs per batch: insert or upsert the records from Paige's one-row-per-document CSV, then insert the PDFs as ContentVersion files linked to those records — no subscription, no automation platform.
Send Paige documents to Salesforce with Zapier or Make
Build the Zap or Make scenario that watches Paige's SFTP export folder, finds or creates the Salesforce record from each document's fields, and attaches the PDF as a File on that record.
SAP Business One3 guides
Connect Paige to SAP Business One
Two working paths from Paige into SAP Business One: the Data Transfer Workbench to load a batch of A/P invoices from Paige's CSV, or an integration with the Service Layer that creates each A/P invoice and attaches the PDF. Which to pick, what lands in SAP B1, and the step-by-step guides.
Import Paige invoices into SAP Business One with the Data Transfer Workbench
Turn a batch of invoices Paige read into SAP Business One A/P invoices with the Data Transfer Workbench: fill DTW's Documents and Document_Lines templates from Paige's one-row-per-document CSV, map them to the Purchase Invoices object, and import.
Integrate Paige with the SAP Business One Service Layer
For developers: the Service Layer calls that turn a Paige invoice into an SAP Business One A/P invoice with the PDF attached — log in, upload the PDF to Attachments2, then POST the PurchaseInvoices document with the attachment entry — fed from Paige's SFTP export files or the Paige API.
SharePoint3 guides
Connect Paige to SharePoint
Two working paths from Paige into SharePoint Online: a Power Automate flow that files each finished document in a library and fills its metadata columns from Paige's extracted fields, or a synced library folder that Paige's export lands in directly. Which to pick, what ends up in SharePoint, and the step-by-step guides.
Export Paige documents to a synced SharePoint folder
The no-license path: sync a SharePoint library to a PC with the OneDrive app, run an SFTP server on that PC pointed into the synced folder, and Paige's export lands in the library by itself — PDFs only, no metadata columns, nothing to build.
Send Paige documents to SharePoint with Power Automate
Build the Power Automate flow that watches Paige's SFTP export folder, reads each document's field values, creates the PDF in a SharePoint library with a meaningful name, and fills the library's metadata columns — vendor, invoice number, date, amount — from what Paige extracted.
Xero4 guides
Connect Paige to Xero
Three working paths from Paige into Xero: an automation on Zapier or Make that creates each bill from Paige's extracted fields and attaches the PDF; forwarding Paige's PDFs to Xero's bills email address so Xero drafts the bill; or Xero's CSV bill import for batches. Which to pick, what lands in Xero, and the step-by-step guides.
Email Paige invoices to Xero bills
The lowest-effort route into Xero: a one-step automation emails each PDF Paige finishes to your organisation's bills email address, and Xero creates a draft bill from it. Paige's own field values aren't sent — just the clean, searchable PDF — so you review the draft in Xero as usual.
Import Paige invoices into Xero from CSV
Export a batch of invoices from Paige, copy the one-row-per-document CSV into Xero's bill import template, and load it — draft bills with contact, dates, reference, and amount filled from Paige, no subscription, PDFs attached by hand if you want them.
Send Paige invoices to Xero with Zapier or Make
Build the Zap or Make scenario that watches Paige's SFTP export folder, creates the bill in Xero from Paige's extracted fields, and attaches the PDF — so every invoice Paige finishes becomes a Xero bill on its own.
Other guides10 guides
Connect Paige to any app with Zapier, Make, or Power Automate
The one pattern behind most Paige integrations: Paige drops each finished document and its data on an SFTP server, an automation platform picks the file up, and its built-in connector creates the record in QuickBooks, SharePoint, Salesforce, monday.com, or whatever you run — no code, no server.
Connect Paige to ClickUp
Create a ClickUp task for every document Paige finishes — name, description, and custom fields filled from Paige's extracted values, the PDF attached — with a Zapier Zap or a Make scenario watching Paige's SFTP export folder.
Connect Paige to Google Sheets and Excel
Get Paige's extracted data into a spreadsheet: open the one-row-per-document CSV Paige exports, or have Zapier, Make, or Power Automate append a row to a Google Sheet or an Excel table for every document Paige finishes — with a link to the PDF.
Connect Paige to M-Files
M-Files reads a same-named XML file next to every imported document — and that is exactly what Paige writes. Point Paige at a folder the M-Files server can see, create an external file source that reads Paige's XML with XPath, and finished documents arrive in the vault with their class and properties already set.
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.
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.
Connect Paige to OnBase
Get Paige's finished documents into Hyland OnBase through Document Import Processor (DIP): Paige exports each document with its data to an SFTP folder, a Power Automate flow writes the DIP index file and drops the PDF on the import share, and OnBase's scheduled DIP process files the documents with their keywords set.
Export Paige documents to Content Central
Paige's native Content Central export: point a scan job at your Content Central server, sign in as a capture user, map each Paige document type to a catalog and document type, choose whether documents file directly or wait in the Coding Queue, and map the fields so they arrive indexed.
Export Paige documents to Nucleus One
Paige's native Nucleus One export: generate an API key in Nucleus One, connect a scan job to an organization and project, map each document type's fields, and let finished documents file themselves — tagged by document type, with their field values already filled in.
Integrate your own system with the Paige API
Create a Paige API key, call the same REST API the Paige web app uses, and pull finished documents, their field values, and their PDFs into your own database or application — or push files in for processing.