AdemeroHelp

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.

Administrators1 hourVerified 2026-09-05

Before you begin

  • DocuWare Cloud, with a user allowed to store into the target file cabinet
  • A Make account on a plan that includes the SFTP app (paid tiers)
  • 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, a Make scenario stores every document Paige finishes into your DocuWare Cloud file cabinet within minutes, with the index fields filled from what Paige extracted.

The scenario is five modules: SFTP watch → filter to the data file → JSON parse → SFTP get the PDF → DocuWare Store to file cabinet. Paige uploads the PDF before the data file, so the PDF is always there when the scenario runs.

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 unless you'll review in DocuWare's document tray. Click Save.

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

Step 2 — Note what the scenario needs from DocuWare

  • Your DocuWare organization URL (the address you sign in at).
  • The file cabinet and the store dialog to use.
  • A DocuWare user for the integration — ideally a dedicated one named for the job, with store rights on that cabinet. Make signs in as this user when you create the connection.

Step 3 — Build the scenario

  1. SFTP → Watch files in a folder. Create the connection: Host, Port 22, Auth Type Username and Password, and the credentials. Set the folder to the scan job's folder. This is the trigger.

  1. Filter on the line after it: File name Ends with .json. Without it the scenario runs four times per document.

  1. SFTP → Get a file for the triggered file, then JSON → Parse JSON with that file's data as input. Run the scenario once with a real Paige file so Make learns the structure; afterwards every Paige field appears as a mappable item under fields.

  1. SFTP → Get a file again, with the path set to the folder plus the parsed metadata.pdf_file. This is the PDF.

  1. DocuWare → Store to file cabinet. Create the connection: choose DocuWare oAuth2 as the connection type, enter your organization's address in DocuWare Server URL, and sign in as the integration user when the login window appears.

    • Select the file cabinet and the store dialog. Make then lists each field of that dialog with its name and field type.
    • Map each index field to the matching parsed Paige field. In Map mode you can enter an expression instead — use Make's parseDate() for date fields and parseNumber() for amounts, because Paige exports values as text exactly as they appear on the page.
    • Map the file data from module 4 into the file input.

  1. Set the scheduling (every 15 minutes is the default on the basic plan; shorten it if you like) and turn the scenario on.

Note

To have someone confirm the indexing in DocuWare, use Import to document tray instead of Store to file cabinet. The document lands in the tray with the values pre-filled.

Step 4 — Test it

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

  2. In Make, open the scenario's History. What you should see: one run with all five modules green.

  3. In DocuWare, open the file cabinet. What you should see: the document with the mapped index fields filled from Paige's values, and selectable text when you open it.

When it doesn't work

SymptomWhere to look
The scenario never triggersWrong folder in the watch module, or the scenario is off. Check the History for errors.
Runs four times per documentThe .json filter is missing.
Parse JSON shows no fields to mapRun the scenario once with a real file so the data structure is learned, then reopen the DocuWare module.
Store module errors on a fieldA date or number field received text. Wrap the mapping in parseDate() / parseNumber(). A required dialog field left empty also fails the store.
Connection failsSign in again as the integration user; if the user's password changed, the connection must be re-authorized.

If the Paige side is the problem, contact Ademero support with the scan job name and the message from Test Connection.