Send Paige documents to DocuWare with Power Automate

Step 1 — Point Paige at your SFTP server

1. 1

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

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

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

4. 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 plan to review in DocuWare's document tray instead. Click Save.

Step 2 — Create a DocuWare API key for Power Automate

1. 1

   Sign in to DocuWare Cloud as the user the flow should act as — ideally a dedicated user named for the job, with store rights on the target file cabinet.

2. 2

   Open Configurations, go to the Integrations section, and click Power Automate API Keys. If you don't see it, your user lacks the permission; a DocuWare administrator can grant it.

3. 3

   Click Create API Key, enter a Name (and optionally a Description), and click Create.

4. 4

   Copy the key now. This is the only time DocuWare shows it in full.

Step 3 — Build the flow

1. 1

   Trigger — SFTP - SSH: When a file is added or modified. Create the connection with Host server address, User name, Password, and Port number 22. In Folder, pick the scan job's folder. Leave Include file content on.

2. 2

   Condition. Add a Condition: File name ends with .json. Everything below goes in the If yes branch. (Without this the flow runs four times per document, once per file Paige writes.)

3. 3

   Parse JSON. Content: the trigger's File content. Schema: click Use sample payload to generate schema and paste a real .json from the folder. Each Paige field becomes a token.

4. 4

   SFTP - SSH: Get file content using path. File path: the folder plus the parsed pdf_file token, for example /paige/invoices/@{body('Parse_JSON')?['metadata']?['pdf_file']}. This is the PDF.

5. 5

   DocuWare: Store to file cabinet. On first use, create the connection: a Connection Name and the API key from Step 2.

   • File Cabinet: pick the cabinet.
   • Store Dialog: pick the dialog.
   • File Contents: the File content output of the previous step.
   • Index Data: a JSON object keyed by database field name, with values taken from the Parse JSON tokens:

   {
     "COMPANY": "@{body('Parse_JSON')?['fields']?['Vendor Name']}",
     "INVOICE_NUMBER": "@{body('Parse_JSON')?['fields']?['Invoice Number']}",
     "INVOICE_DATE": "2026-08-28T00:00:00.000Z",
     "AMOUNT": 1284.50
   }
   

   Dates must be in ISO 8601 form (YYYY-MM-DDT00:00:00.000Z) and numbers must be plain numbers. Paige exports values as text exactly as they appear on the page, so convert with expressions — formatDateTime(...) for dates and float(replace(..., ',', '')) for amounts — rather than pasting the raw token. Keyword fields take an array (["Value1","Value2"]) and table fields take an array of rows.

6. 6

   Save the flow. What you should see: the flow checker reports no errors.

Step 4 — Test it

1. 1

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

2. 2

   In Power Automate, open the flow's 28-day run history. What you should see: one successful run, triggered by the .json file, within a few minutes.

3. 3

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

When it doesn't work