Skip to main content
Google Document AI reads scanned and digital documents and returns every word and line with its position on the page and a confidence score. Noxus uses it as an OCR provider: document extraction fills your fields with the language model, and the boxes that show a reviewer where each value is printed come from Document AI. The processing runs in your own Google Cloud project, in the region you choose, and Google bills that project directly.

​
What you need

  • A Google Cloud project with billing enabled.
  • An Enterprise Document OCR processor in that project. Other processor types, such as Invoice Parser or Custom Extractor, are refused, because they do not return line-level positions.
  • A service account key from the same project that can use the processor.

​
Set it up

1

Enable the Document AI API

In Google Cloud Console, open APIs & Services → Library, search for Cloud Document AI API, and click Enable.
2

Create an OCR processor

Open Document AI → Processor gallery, choose Enterprise Document OCR, and create it. Pick the region that matches your data residency: eu or us. One OCR processor per region is enough; Noxus finds it by itself.
3

Create a service account and key

Open IAM & Admin → Service Accounts, create a service account for Noxus, and grant it the Document AI Viewer role (roles/documentai.viewer) on the project. Noxus needs this role to find and check the processor, and to send documents to it. Then open Keys → Add Key → Create new key → JSON and download the key file.
4

Connect it in Noxus

Open Workspace control → Connections, click Add connection, and choose Google Document AI. Choose the Location of the processor and paste the whole key file into Service account JSON. Noxus reads the project from the key.Leave OCR processor ID empty unless the project has several OCR processors in that location. In that case, copy the ID of the one to use from the processor’s details page in the Document AI console.Noxus checks the processor when you save. On success the status is Active, and the connection’s Metadata tab shows the project, the processor that was used with its ID and version, and the service account’s email. The key itself is never shown again.

​
When the connection is Invalid

The status shows Invalid, and the connection’s Metadata tab shows the reason:

​
Limits

  • Google reads at most 15 pages per request, so Noxus sends longer PDFs in parts of 15 pages. Each part can be up to 40 MB.
  • Pricing follows Google’s Document AI OCR price list and is charged to your project.