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.
Every document Paige finishes can land in Box (box.com) as a searchable PDF with no one uploading anything. Use Box Drive and a folder on a PC, or an automation that also names each file from its own contents.
Box has no folder-watching import of its own, so Paige reaches it in one of two ways.
What lands in Box
| Box Drive path | Automation path | |
|---|---|---|
| The searchable PDF | In the Box folder you choose, with Paige's generated filename | In the folder you choose, named from Paige's fields (for example INV-20441 – Acme Office Supply.pdf) |
Paige's data files (.json, .xml, .csv) | Land alongside the PDF | Not uploaded unless you want them |
| Where it runs | On a PC that stays on and signed in | In the cloud; nothing on-premises |
Box's full-text search reads the PDF text, so documents are findable by their contents. If you use Box metadata templates, the Zapier path can also fill them (Add Metadata to File), which the automation guide shows.
Pick a path
| Path | Choose it when | Guide |
|---|---|---|
| Box Drive folder | You have a PC that stays on, you're fine with Paige's filenames, and you don't want another subscription | Export Paige documents to a Box Drive folder |
| Automation (Zapier, Make, or Power Automate) | You want files named from their contents, optionally with Box metadata filled, and nothing running on a PC | Send Paige documents to Box with an automation |