List Processors

document_ai.list_processors
ActionGoogle Cloudconnection required

Calls the Document AI API GET /v1/projects/{p}/locations/{l}/processors.

List Document AI processors in a project and location.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Document AI
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location, processor_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Processor location: us or eu (overrides connection).
stringNo———
page_size
Max processors (1-100).
numberNo100≥ 1—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "page_size": 100
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
count
number—
processors[].processor_id
string—
processors[].display_name
string—
processors[].type
string—
processors[].state
string—
processors[].name
string—
{
  "count": 0,
  "ok": false,
  "processors": [
    {
      "display_name": "",
      "name": "",
      "processor_id": "",
      "state": "",
      "type": ""
    }
  ]
}

Solutions with Google Document AI

See List Processors run in a workflow.

In a technical demo we add the Google Document AI connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.