The Doc AI - Operation task lets you check the status of a long-running operation (LRO) in the Document AI processor. The Document AI processor creates an LRO every time you send a Batch Process request.
Cloud Document AI is a Google Cloud service that allows you 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.
Before you begin
Ensure that you perform the following tasks in your Google Cloud project before configuring the Doc AI - Operation task:
Enable the Cloud Document AI API (documentai.googleapis.com) in your Google Cloud project before configuring the Doc AI - Operation task.
Create an authentication profile. Application Integration uses an authentication profile to connect to an authentication endpoint for the Doc AI - Operation task.
The Integrations page appears listing all the integrations available in the Google Cloud project.
Select an existing integration or click Create integration to create a new one.
If you are creating a new integration:
Enter a name and description in the Create Integration pane.
Select a region for the integration.
Select a service account for the integration. You can change or update the service account details of an integration any time from the infoIntegration summary pane in the integration toolbar.
Click Create. The newly created integration opens in the integration editor.
In the integration editor navigation bar, click Tasks to view the list of available tasks and connectors.
Click and place the Doc AI - Operation element in the integration editor.
Click the Doc AI - Operation element on the designer to view the Doc AI - Operation task configuration pane.
Go to Authentication, and select an existing authentication profile that you want to use.
Optional. If you have not created an authentication profile prior to configuring the task, Click + New authentication profile and follow the steps as mentioned in Create a new authentication profile.
Go to Task Input, and configure the displayed inputs fields using the following Task input parameters table.
Changes to the inputs fields are saved automatically.
Task input parameters
The following table describes the input parameters of the Doc AI - Operation task:
Property
Data type
Description
Region
String
Cloud Document AI location for the processor. For example: us - United States.
ProjectsId
String
Your Google Cloud project ID.
OperationId
String
The ID of your operation. The ID is the last element of the name of your operation.
Task output
The Doc AI - Operation task returns the details of your long-running operation (LRO), similar to the following sample output:
An error handling strategy for a task specifies the action to take if the task fails due to a temporary error. For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see Error handling strategies.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThe \u003cstrong\u003eDoc AI - Operation\u003c/strong\u003e task allows you to monitor the status of long-running operations (LROs) initiated by the Document AI processor when a \u003cstrong\u003eBatch Process\u003c/strong\u003e request is sent.\u003c/p\u003e\n"],["\u003cp\u003eTo use the \u003cstrong\u003eDoc AI - Operation\u003c/strong\u003e task, you must first enable the Cloud Document AI API in your Google Cloud project and create an authentication profile.\u003c/p\u003e\n"],["\u003cp\u003eThe task's input parameters include the Cloud Document AI region, your Google Cloud project ID, and the operation ID you wish to check.\u003c/p\u003e\n"],["\u003cp\u003eThe output of the \u003cstrong\u003eDoc AI - Operation\u003c/strong\u003e task provides detailed information about the status of the LRO, such as whether it succeeded, failed, or is still in progress.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003cstrong\u003eDoc AI - Operation\u003c/strong\u003e task falls under Pre-GA features which are subject to the Pre-GA Offerings Terms and are available "as is" with potential limited support.\u003c/p\u003e\n"]]],[],null,["# Doc AI - Operation task\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nDoc AI - Operation task\n=======================\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThe **Doc AI - Operation** task lets you check the [status](/document-ai/docs/long-running-operations#getting_details_about_a_long-running_operation) of a long-running operation (LRO) in the Document AI processor. The [Document AI processor](/document-ai/docs/overview#dai-processors) creates an LRO every time you send a **Batch Process** request.\n\n\n[Cloud Document AI](https://cloud.google.com/document-ai/docs) is a Google Cloud service that allows you 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.\n\nBefore you begin\n----------------\n\nEnsure that you perform the following tasks in your Google Cloud project before configuring the **Doc AI - Operation** task:\n\n1. Enable the Cloud Document AI API (`documentai.googleapis.com`) in your Google Cloud project before configuring the **Doc AI - Operation** task.\n\n\n [Enable the Cloud Document AI API](https://console.cloud.google.com/flows/enableapi?apiid=documentai.googleapis.com)\n2. Create an [authentication profile](/application-integration/docs/configuring-auth-profile#createAuthProfile). Application Integration uses an authentication profile to connect to an authentication endpoint for the **Doc AI - Operation** task.\n\n For information about granting additional roles or permissions to a service account, see [Granting, changing, and revoking access](/iam/docs/granting-changing-revoking-access).\n\nConfigure the Doc AI - Operation task\n-------------------------------------\n\n1. In the Google Cloud console, go to the **Application Integration** page.\n\n [Go to Application Integration](https://console.cloud.google.com/integrations)\n2. In the navigation menu, click **Integrations** .\n\n\n The **Integrations** page appears listing all the integrations available in the Google Cloud project.\n3. Select an existing integration or click **Create integration** to create a new one.\n\n\n If you are creating a new integration:\n 1. Enter a name and description in the **Create Integration** pane.\n 2. Select a region for the integration. **Note:** The **Regions** dropdown only lists the regions provisioned in your Google Cloud project. To provision a new region, click **Enable Region** . See [Enable new region](/application-integration/docs/enable-new-region) for more information.\n 3. Select a service account for the integration. You can change or update the service account details of an integration any time from the info **Integration summary** pane in the integration toolbar. **Note:** The option to select a service account is displayed only if you have enabled integration governance for the selected region.\n 4. Click **Create** . The newly created integration opens in the *integration editor*.\n\n\n4. In the *integration editor* navigation bar, click **Tasks** to view the list of available tasks and connectors.\n5. Click and place the **Doc AI - Operation** element in the integration editor.\n6. Click the **Doc AI - Operation** element on the designer to view the **Doc AI - Operation** task configuration pane.\n7. Go to **Authentication** , and select an existing authentication profile that you want to use.\n\n Optional. If you have not created an authentication profile prior to configuring the task, Click **+ New authentication profile** and follow the steps as mentioned in [Create a new authentication profile](/application-integration/docs/configuring-auth-profile#createAuthProfile).\n8. Go to **Task Input** , and configure the displayed inputs fields using the following [Task input parameters](#params) table.\n\n Changes to the inputs fields are saved automatically.\n\nTask input parameters\n---------------------\n\n\nThe following table describes the input parameters of the **Doc AI - Operation** task:\n\nTask output\n-----------\n\nThe **Doc AI - Operation** task returns the details of your long-running operation (LRO), similar to the following sample output: \n\n```\n{\n \"name\": \"projects/[PROJECT_ID]/locations/[LOCATION]/operations/[OPERATION_ID]\",\n \"metadata\": {\n \"@type\": \"type.googleapis.com/google.cloud.documentai.v1.BatchProcessMetadata\",\n \"state\": \"SUCCEEDED\",\n \"stateMessage\": \"Processed 1 document(s) successfully\",\n \"createTime\": \"TIMESTAMP\",\n \"updateTime\": \"TIMESTAMP\",\n \"individualProcessStatuses\": [\n {\n \"inputGcsSource\": \"[INPUT_BUCKET_FOLDER]/DOCUMENT1.ext\",\n \"status\": {},\n \"outputGcsDestination\": \"OUTPUT_BUCKET_FOLDER/[OPERATION_ID]/0\",\n \"humanReviewStatus\": {\n \"state\": \"ERROR\",\n \"stateMessage\": \"Sharded document files are not supported for human review.\"\n }\n }\n ]\n },\n \"done\": true,\n \"response\": {\n \"@type\": \"type.googleapis.com/google.cloud.documentai.v1.BatchProcessResponse\"\n }\n}\n \n```\n\n\u003cbr /\u003e\n\nError handling strategy\n-----------------------\n\n\nAn error handling strategy for a task specifies the action to take if the task fails due to a [temporary error](/application-integration/docs/error-handling). For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see [Error handling strategies](/application-integration/docs/error-handling-strategy).\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Add [edges and edge conditions](/application-integration/docs/edge-overview).\n- [Test and publish](/application-integration/docs/test-publish-integrations) your integration.\n- Configure a [trigger](/application-integration/docs/how-to-guides#configure-triggers).\n- Add a [Data Mapping task](/application-integration/docs/data-mapping-task).\n- See [all tasks for Google Cloud services](/application-integration/docs/how-to-guides#configure-tasks-for-google-cloud-services)."]]
