Google Document AI
Extract text and entities from documents with Google Document AI (Google OAuth2).
OCNORA ships 6 typed Google Document AI operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Document AI
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Document AI
Operations, grouped by what they do to your data.
Create and send 1
Read and search 2
Delete and cancel 1
Other operations 2
A sample Google Document AI workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Document AI trigger is needed.
- 2Get Processordocument_ai.get_processorGets a processor detail.
- 3Batch Processdocument_ai.batch_processStart an async batch job from gs:// input (file or prefix) to a gs:// prefix.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 6
- Batch ProcessStart an async batch job from gs:// input (file or prefix) to a gs:// prefix.document_ai.batch_process
- Create ProcessorCreates a processor from the ProcessorType provided.document_ai.create_processor
- Delete ProcessorDeletes the processor, unloads all deployed model artifacts if it was enabled and then deletes all artifacts associated with this processor.document_ai.delete_processor
- Get ProcessorGets a processor detail.document_ai.get_processor
- List ProcessorsList Document AI processors in a project and location.document_ai.list_processors
- Process DocumentRun a Document AI processor on a PDF/image; emits text and entities.document_ai.process_document
Where Google Document AI fits
Google Document AI questions
- How does OCNORA authenticate with Google Document AI?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Document AI?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Document AI operation I need is not listed?
- Where Google Document AI has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Document AI?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Document AI calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Document AI workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.