The Workflows - Execute task lets you execute a workflow in Cloud Workflows. Executing a workflow runs the current workflow definition associated with the workflow.
Cloud Workflows is a Google Cloud service that allows you to fully-manage and orchestrate runtime services in the order you define.
Before you begin
Ensure that you perform the following tasks in your Google Cloud project before configuring the Workflows - Execute task:
Enable the Workflow Executions API (workflowexecutions.googleapis.com).
Create an authentication profile. Application Integration uses an authentication profile to connect to an authentication endpoint for the Workflows - Execute task.
Configure the Workflows - Execute task
In the Google Cloud console, go to the Application Integration page.
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 Workflows - Execute element in the integration editor.
Click the Workflows - Execute element on the designer to view the Workflows - Execute 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 Workflows - Execute task:
Property
Data type
Description
Region
String
Region where you want to create a new Workflow execution. For example, us-central1.
The Workflows - Execute task returns the newly created instance of the Workflow execution.
Error handling strategy
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-09-03 UTC."],[[["\u003cp\u003eThe \u003cstrong\u003eWorkflows - Execute\u003c/strong\u003e task in Application Integration allows you to run a workflow within Cloud Workflows, a Google Cloud service for orchestrating runtime services.\u003c/p\u003e\n"],["\u003cp\u003eBefore using the \u003cstrong\u003eWorkflows - Execute\u003c/strong\u003e task, you must enable the Workflow Executions API and create an authentication profile, ensuring the service account has the necessary IAM permission \u003ccode\u003eworkflows.executions.create\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003cstrong\u003eWorkflows - Execute\u003c/strong\u003e task requires input parameters such as Region, ProjectsId, WorkflowsId, and Request (in JSON format) to specify the workflow to be executed.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003cstrong\u003eWorkflows - Execute\u003c/strong\u003e task is currently a Pre-GA feature, meaning it is subject to specific terms and might have limited support, and it is available "as is".\u003c/p\u003e\n"],["\u003cp\u003eThe task returns a newly created instance of the Workflow execution as its output, and you can define an error handling strategy for the task in case of temporary failures.\u003c/p\u003e\n"]]],[],null,["# Workflows - Execute task\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nWorkflows - Execute 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 **Workflows - Execute** task lets you execute a workflow in Cloud Workflows. Executing a workflow runs the current workflow definition associated with the workflow.\n\n[Cloud Workflows](/workflows/docs/overview) is a Google Cloud service that allows you to fully-manage and orchestrate runtime services in the order you define.\n\nBefore you begin\n----------------\n\nEnsure that you perform the following tasks in your Google Cloud project before configuring the **Workflows - Execute** task:\n\n1. Enable the Workflow Executions API (`workflowexecutions.googleapis.com`).\n\n\n [Enable the Workflow Executions API](https://console.cloud.google.com/flows/enableapi?apiid=workflowexecutions.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 **Workflows - Execute** task. **Note:** If you're creating an authentication profile of [Service account](/application-integration/docs/configure-authentication-profiles#service-account) type, then ensure that the service account is assigned with the IAM role that contains the following IAM permission(s):\n | - `workflows.executions.create`\n |\n | To know about IAM permissions and the predefined IAM roles that grant them, see [IAM permissions reference](/iam/docs/permissions-reference#search).\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 Workflows - Execute 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 **Workflows - Execute** element in the integration editor.\n6. Click the **Workflows - Execute** element on the designer to view the **Workflows - Execute** 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 **Workflows - Execute** task:\n\nTask output\n-----------\n\nThe **Workflows - Execute** task returns the newly created instance of the Workflow execution.\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)."]]
