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

Product: paige · Audience: system-administrator · Time: 1 hour · Last verified: 2026-09-05

Canonical: https://help.ademero.com/paige/integrations/send-paige-documents-to-docuware-with-power-automate

**At the end of this guide, a Power Automate flow stores every document Paige finishes into your DocuWare Cloud file cabinet within a few minutes, with the index fields filled from what Paige extracted — no store dialog to fill, no upload step.**

The flow has five steps: *SFTP trigger → keep only the data file → Parse JSON → get the PDF → DocuWare Store to file cabinet.* Paige uploads the PDF before the data file, so by the time the flow fires the PDF is always there.

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

Open port 22 on your firewall to Paige's address ranges — [Outbound IP ranges for firewall allow-lists](/paige/document-processing/outbound-ip-ranges-for-firewall-allow-lists).

## Step 2 — Create a DocuWare API key for Power Automate

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. 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. Click **Create API Key**, enter a **Name** (and optionally a **Description**), and click **Create**.
4. Copy the key now. This is the only time DocuWare shows it in full.

While you're in DocuWare, note two things you'll need in the flow: the **file cabinet** name and the **store dialog** you want used, and the **database field names** of the index fields (Configurations > File Cabinets > your cabinet > **Database Fields**; they're upper-case, like `INVOICE_NUMBER`). The connector addresses fields by database name, not display name.

## Step 3 — Build the flow

In Power Automate, create an **Automated cloud flow**.

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. **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. **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. **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. **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:
   
   ```json
   {
     "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. **Save** the flow. **What you should see:** the flow checker reports no errors.

> **NOTE:** If you'd rather have someone confirm the indexing in DocuWare, use **Import to document tray** instead of **Store to file cabinet** at step 5. The document appears in the tray with the index values pre-filled, and a person stores it with one click.

> **IMPORTANT:** DocuWare's connector is not yet supported in the *new* Power Automate designer. If the DocuWare actions don't appear or won't configure, switch the designer to the classic view with the toggle at the top right.

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

| Symptom | Where to look |
| --- | --- |
| The flow never runs | Wrong folder in the trigger, or the folder is a subfolder (the trigger doesn't watch subfolders). Files over 50 MB are skipped by this trigger. |
| Runs four times per document | The `.json` condition is missing or misplaced. |
| Store step fails with `400` | A required index field is missing from **Index Data**, or a value has the wrong type (a text date, a number with a comma). Check the expression conversions. |
| Store step fails with `401` | The API key is wrong or was deleted in DocuWare's **Power Automate API Keys** page. |
| Store step fails with `404` | The file cabinet or store dialog isn't available to the API key's user. |
| Fields arrive empty | The Parse JSON schema was generated from a sample missing those fields. Regenerate from a `.json` of the right document type. |

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

## What's next

- [Connect Paige to DocuWare](https://help.ademero.com/paige/integrations/connect-paige-to-docuware)
- [Connect Paige to any app with Zapier, Make, or Power Automate](https://help.ademero.com/paige/integrations/connect-paige-to-any-app-with-zapier-make-or-power-automate)