Stay organized with collections Save and categorize content based on your preferences.

See the supported connectors for Application Integration.

Call Integration task

The Call Integration task lets you run other integrations (sub-integrations) from your main integration.

This task uses the API Trigger ID as a handle to identify the integrations to run. For example, if you specify the API Trigger ID as api_trigger/APITriggerX, the task runs all the sub-integrations that have the api_trigger/APITriggerX trigger ID. After running a sub-integration, you can also read the response of the sub-integration in your main integration. Use this task to run sub-integrations as dependencies of the main integration.

Configure the Call Integration task

To configure the Call Integration task:

  1. In the Google Cloud console, go to the Application Integration page.

    Go to Application Integration

  2. In the navigation menu, click Integrations.

    The Integrations List page appears.

  3. Select an existing integration or create a new integration by clicking Create integration.

    If you are creating a new integration:

    1. Enter a name and description in the Create Integration dialog.
    2. Select a Region for the integration from the list of supported regions.
    3. Click Create.

    This opens the integration in the integration designer.

  4. In the integration designer navigation bar, click +Add a task/trigger > Tasks to view the list of available tasks.
  5. Click and place the Call Integration element in the integration designer.
  6. Click the Call Integration task element on the designer to view the Call Integration task configuration pane.
  7. Configure the displayed fields using the Configuration properties for the task as detailed in the tables below.

    All changes to the properties are saved automatically.

Configuration properties

The following table describes the configuration properties of the task.
Property Data type Description
API Trigger ID String Trigger ID of the sub-integration to run.

This value is available in the Trigger ID field of the API Trigger in the sub-integration.

To run the sub-integrations, you can choose any one of the following options:

  • Run all integrations with this API Trigger ID: Runs all integrations that have the same API Trigger ID. For example, if integration A and integration B, have the same API Trigger ID, both the integrations A and B are run.

    Note: If you select this option, the response from the sub-integrations will not be available in the main integration. If you want to access the response of the sub-integrations, select the Run a single integration option.

  • Run a single integration: Runs only the integration specified in the Integration name field. You can access the response from the sub-integrations by configuring the Collect values from sub-integration output(s) section.

Map to sub-integration input(s) N/A

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 productID variable to the subIntProductID sub-integration variable, you would select productID from the Integration variable to map from field and enter subIntProductID in the Subintegration input to map to field.

If the Run a single integration option is selected with a SYNC execution strategy, the UI displays the Map values to subintegration output(s) section. This lets you map the sub-integration output variables to the main integration variables. Select the sub-integration variable from the Subintegration output to map from dropdown and the corresponding main integration variable from the Integration variable to map to dropdown.

Execution strategy N/A 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 the Execution delay (in milliseconds). When set, this specifies the time delay until the integration is run.

executionIds(TASK_NAME) String Output variable containing the execution IDs of the sub-integrations.

Retry on failure

You can configure various retry strategies to handle errors in a task. The retry strategies allow you to specify how to rerun the task or integration in case of an error. For more information, see Error handling strategies.