Can HumDay connect to Google Cloud Document AI?

Yes. HumDay reads Google Cloud Document AI's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 21 operations are documented.

Do I need to write code to automate Google Cloud Document AI?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Cloud Document AI account.

What can HumDay do in Google Cloud Document AI?

14 of the 21 documented operations change something in Google Cloud Document AI, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Cloud Document AI account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Cloud Document AI is held behind that approval.

Automate Google Cloud Document AI

HumDay reads Google Cloud Document AI’s own published API description and derives 21 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Cloud Document AI is

Service to parse structured information from unstructured or semi-structured documents using state-of-the-art Google AI such as natural language, computer vision, translation, and AutoML.

API host: documentai.googleapis.com

What HumDay can do in Google Cloud Document AI

14 documented operations change something in Google Cloud Document AI.

POSTSend a document for Human Review./v1beta3/{humanReviewConfig}:reviewDocument
POSTCreates a processor from the type processor that the user chose./v1beta3/{parent}/processors
POSTProcesses a single document./v1beta3/{name}:process
POSTTrains a new processor version./v1beta3/{parent}/processorVersions:train
DELETEDeletes the processor version, all artifacts under the processor version will be deleted./v1beta3/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1beta3/{name}:cancel
POSTDeploys the processor version./v1beta3/{name}:deploy
POSTEnables a processor/v1beta3/{name}:enable
POSTDisables a processor/v1beta3/{name}:disable
POSTUndeploys the processor version./v1beta3/{name}:undeploy
POSTLRO endpoint to batch process many documents./v1beta3/{name}:batchProcess
POSTSet the default (active) version of a Processor that will be used in ProcessDocument and BatchProcessDocuments./v1beta3/{processor}:setDefaultProcessorVersion
POSTEvaluates a ProcessorVersion against annotated documents, producing an Evaluation./v1beta3/{processorVersion}:evaluateProcessorVersion
POSTImports a processor version from source processor version./v1beta3/{parent}/processorVersions:importProcessorVersion

What HumDay can read from Google Cloud Document AI

These are the operations a schedule or a trigger can watch.

GETGets a processor type detail./v1beta3/{name}
GETFetches processor types./v1beta3/{parent}:fetchProcessorTypes
GETLists information about the supported locations for this service./v1beta3/{name}/locations
GETLists all processors which belong to this project./v1beta3/{parent}/processors
GETRetrieves a set of evaluations for a given processor version./v1beta3/{parent}/evaluations
GETLists the processor types that exist./v1beta3/{parent}/processorTypes
GETLists all versions of a processor./v1beta3/{parent}/processorVersions

How automating Google Cloud Document AI works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Cloud Document AI account.
Grant access, then go live. You approve the specific Google Cloud Document AI operations it may use — and only those.