Call Integration task
TheCall Integration task lets you invoke or call other integrations created within your Google Cloud project.
TheCall Integration task is useful in scenarios where you need to define multiple small integrations (sub-integrations) that is controlled using a main integration (parent integration). After running a sub-integration, you can also read the response of the sub-integration in your main integration.
Before you begin
- TheCall Integration task uses the API trigger to identify and call other integrations and sub-integrations. Therefore, you must ensure that the integrations you want to call are configured using the API trigger. For information about configuring an API trigger seeAPI trigger.
- Ensure that you haveattached a user-managed service account to your integration. If your integration does not have user-managed service account configured, then by default thedefault service account (
service-PROJECT_NUMBER@gcp-sa-integrations.iam.gserviceaccount.com) is used for authentication. - Ensure that your service account has theApplication Integration Invoker IAM role. For information about granting roles to a service account, seeManage access to service accounts.
Configure the Call Integration task
To configure theCall Integration task:
- In the Google Cloud console, go to theApplication Integration page.
- In the navigation menu, clickIntegrations.
TheIntegrations page appears listing all the integrations available in the Google Cloud project.
- Select an existing integration or clickCreate integration to create a new one.
If you are creating a new integration:
- Enter a name and description in theCreate Integration pane.
- Select a region for the integration.Note: TheRegions dropdown only lists the regions provisioned in your Google Cloud project. To provision a new region, clickEnable Region. SeeEnable new region for more information.
- Select a service account for the integration. You can change or update the service account details of an integration any time from theIntegration 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.
- ClickCreate. The newly created integration opens in theintegration editor.
- In theintegration editor navigation bar, clickTasks to view the list of available tasks and connectors.
- Click and place theCall Integration element in the integration editor.
- Click theCall Integration task element on the designer to view theCall Integration task configuration pane.
- Configure the following sub integration details:
- API Trigger ID: Type theAPI trigger ID of the integration that you want to call. You can call a single integration or multiple integrations with the same trigger ID.
- Run all integrations with this API Trigger ID: Select this option to call all the integrations that have the same APITrigger ID.
For example, if integration
Aand integrationB, have the same APITrigger ID, both the integrationsAandBare run. - Run a single integration: Select this option to call only the integration specified in theIntegration name field. You can access and map the response from the sub-integration by configuring the fields detailed inMap sub-integration response variables.
- Execution strategy: Select the execution modes for the sub-integrations that you want to call.
- SYNC: Runs the sub-integration in synchronous mode. In this mode, the main integration waits for the sub-integrations to complete before continuing with the downstream tasks.
- ASYNC: Runs the sub-integration in asynchronous mode. In this mode, the main integration does not wait for the sub-integrations to complete. Immediately after calling the sub integrations, the main integration runs the downstream tasks.
If this option is selected, set theExecution delay (in milliseconds). When set, this specifies the time delay until the integration is run.
All changes to the properties are saved automatically.
Map sub-integration response variables
The following table describes the configuration properties to map variables between the main integration and sub-integrations:| Property | Description |
|---|---|
Map to sub-integration input(s) | Maps values from the main integration to the sub-integration. This field takes values in the form of key-value pairs, where the key is a variable in the main integration, and the value is the corresponding input variable in the sub-integration. For example, if you want to map the main integration's |
Map values to sub-integration output(s) | Maps the sub-integration output variables to the main integration variables. ClickSubintegration output to map from and select the sub-integration. ClickIntegration variable to map to and select the corresponding main integration variable. Note: This field is only displayed when theRun a single integration option is selected with theSYNC execution strategy. |
Best practices
For information about the usage limits that apply to theCall Integration task, see Usage limits.
Error handling strategy
An error handling strategy for a task specifies the action to take if the task fails due to atemporary error. For information about how to use an error handling strategy, and to know about the different types of error handling strategies, seeError handling strategies.
Quotas and limits
For information about quotas and limits, seeQuotas and limits.
What's next
- Learn aboutall tasks and triggers.
- Learn how totest and publish an integration.
- Learn abouterror handling.
- Learn aboutintegration execution logs.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.