Export Paige documents to Nucleus One
Paige's native Nucleus One export: generate an API key in Nucleus One, connect a scan job to an organization and project, map each document type's fields, and let finished documents file themselves — tagged by document type, with their field values already filled in.
Before you begin
- A Nucleus One organization and project the documents should land in, with the fields you want populated already defined on the project
- A Nucleus One user who is a member of that project (the export runs as that user)
- A Paige scan job whose document types and fields are set up
At the end of this guide, every document Paige finishes appears in your Nucleus One project as a searchable PDF, tagged with its document type, with its fields already filled from what Paige extracted — no re-keying, no upload step.
This is one of Paige's two built-in destinations (the other is Content Central). Nothing sits between the two products: Paige uploads straight into Nucleus One using an API key you create there.
What lands in Nucleus One
For each exported document, Nucleus One receives:
- The document as a searchable PDF, named after the original scanned or uploaded file.
- A tag equal to the Paige document type's name (for example
Vendor Invoice), so the project's tag filters work immediately. - Field values for every Paige field you mapped to a Nucleus One field. Number and currency fields have their currency symbols stripped so they land as numbers.
- The Paige user who ran the export recorded as the uploader.
Line-item tables are not carried over; they stay in Paige. If you need them downstream, use the automation-platform route as well.
Step 1 — Generate the API key in Nucleus One
In Nucleus One, sign in as the user the export should act as, open the avatar menu at the top right, and choose API Keys.
Click +, and in the Add API Key dialog give it a Name/Description that says what it's for —
Paige export— then click ADD.
Copy the key from the API Key Created alert now. The warning is literal: "This is the ONLY time you will see this key."
The Add API Key dialog and the one-time API Key Created alert in Nucleus One
The key carries that user's access. Documents will appear as uploaded by them, and the export can only reach projects they belong to. Use a dedicated Nucleus One user named for the job (for example "Paige Export") so nobody's personal account becomes an integration dependency.
Step 2 — Connect the scan job
In Paige, open Settings (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose Export.
Click the Nucleus One card. The Nucleus One Configuration dialog opens.
Paste the key into API Key and click Validate.
What you should see:
API key validated successfully!If you seeInvalid API Key. Please try again., the key was mistyped or has been deleted in Nucleus One.
Choose the Organization, then the Project. Both lists come from what the key's user can reach — if the project you expect is missing, add that user to it in Nucleus One first (Manage project users and groups).
The Nucleus One Configuration dialog with the key validated and an organization and project selected
Step 3 — Map each document type's fields
Under Document Types, the dialog lists every document type in the scan job. For each one, each Paige field has a Select N1 Field drop-down listing the project's fields.
Map the fields that matter. Leave a Paige field unmapped and it simply isn't sent.
Pick Nucleus One fields whose type fits the data: a Paige date to a date field, an amount to a number or currency field, everything else to text.
What you should see: the dialog confirms each save; if a mapping fails to save you'll see Failed to update field mappings, which almost always means the Nucleus One field list changed since the dialog loaded — close and reopen it.
One document type expanded in the mapping list, with Paige fields on the left and Nucleus One fields chosen on the right
Step 4 — Connect and turn on auto export
Click Connect at the bottom of the dialog. What you should see:
Connected to Nucleus One successfully!and a green Connected label on the Nucleus One card.
On the Export page, turn on Enable Auto Export and set Auto Export Settings: pick the Document Types to send (or leave empty for all), and decide whether to require Human Reviewed = Reviewed and Auto Field Entry Complete = Yes. For a system of record, require both — documents then leave Paige only after a person has looked at them. Click Save.
Documents already sitting in the scan job aren't sent retroactively. Send those once from the Documents page: click Export, walk the Export Documents dialog (Scope, Filters, Destinations, Confirm), and tick Nucleus One under Destinations.
Check it worked
Process one document through the scan job and, if you required review, review it.
In Nucleus One, open the project. What you should see: the document listed within a minute or two, tagged with its document type name, with the mapped fields populated.
Open the PDF and confirm the text is selectable — that's the searchable layer.
When it doesn't work
| Symptom | What it means |
|---|---|
Invalid API Key. Please try again. | The key is wrong, or it was deleted on the Nucleus One API Keys page. Generate a new one. |
| Organization or project missing from the list | The key's user isn't a member. Fix membership in Nucleus One, then reopen the dialog. |
Failed to load fields | The project has no fields yet, or the user can't see them. Define the fields on the project first. |
| Documents arrive with empty fields | The mapping for that document type is blank, or the document had no field values when it exported. Check the mapping, and consider requiring Auto Field Entry Complete. |
| Nothing arrives | Auto export criteria aren't met, or the document was processed before you enabled auto export. Export it once by hand from the Documents page. |
Still stuck? Contact Ademero support with the scan job name, the Nucleus One organization and project names, and the time you expected the document — never the API key.