Connect Paige to DocuWare

Paige reads the paperwork; DocuWare files it. Every document Paige finishes can land in a DocuWare Cloud file cabinet as a searchable PDF with its index fields — vendor, invoice number, date, amount, whatever your scan job extracts — already filled in, so nobody types them into the store dialog.

DocuWare publishes its own connectors for Microsoft Power Automate and for Make, and both have a Store to file cabinet action that takes a file plus index data. Paige's SFTP export produces exactly those two things for every document. The integration is one short flow on whichever platform your organization already uses.

For each document Paige exports:

• The searchable PDF stored in the file cabinet you choose, through the store dialog you choose.
• Index fields set from Paige's field values — you map each DocuWare field to a Paige field once when you build the flow.
• Optionally, the document goes to a document tray instead, with the index values pre-filled, so a person confirms before it's stored. That's the right choice if you want review to happen in DocuWare rather than in Paige.

Line-item tables can be mapped into a DocuWare table field if your file cabinet has one; the guides show where.

Both need the same two things from you first: an SFTP server Paige can write to, and a DocuWare Cloud user dedicated to the integration. Both are covered inside each guide.

DocuWare Import (the desktop app) can watch a folder and store what it finds, and it can read index data from XML — but only in DocuWare's own control-file format, which is not what Paige writes. Paige's XML would simply be ignored and you'd be back to indexing by hand or by DocuWare's text recognition. The connector paths above carry every field Paige extracted, which is the point of using Paige.