Test and publish integrations

You can test or publish an integration from theintegration editor after you have added and configured the integration with the necessarytriggers,tasks, andedge connections. When you test an integration using the Google Cloud console, the integration is executed in thesynchronous mode.

Required role

To get the permissions that you need to test or publish an integration, ask your administrator to grant you theApplication Integration Service Agent (roles/integrations.serviceAgent) IAM role on the project. For more information about granting roles, seeManage access to projects, folders, and organizations.

You might also be able to get the required permissions throughcustom roles or otherpredefined roles.

Test an integration

Optionally, if you want to verify that your integration is working as intended, you can test it before publishing. Testing an integration lets you experiment with the integration input variable values, and helps in identifying any faults in the integration connection flow.

Note: Integrations that are configured with suspension-based tasks, such asApproval task,Suspend task, orTimer task, cannot be tested beforepublishing the integration.

To test run an integration, select one of the following options:

Console

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

    Go to Application Integration

  2. ClickIntegrations from the left navigation menu to open theIntegrations page.
  3. Select the integration that you want to test.

  4. In the designer navigation bar, clickTest.

    If you have multiple triggers configured in your integration, then select the trigger from which you want to test run your integration. TheTest Integration pane appears.

  5. ClickTest integration.

    Application Integration test runs the integration and displays the execution result in theTest Integration pane:

    • To edit the input variables, clickEdit input variables.
    • To retest the integration, clickRetest integration.
    • To restore the values, clickRestore values.
    • To view and inspect theexecution logs of the test run, clickView logs.
    • If you haveenabled Cloud Logging, then to view logs in Cloud Logging, clickView Cloud logs.
    • To edit the integration without creating a new version of the integration, clickEdit integration.
    • To close the test operation and return to the integration editor, clickClose.

API

Call theprojects.locations.integrations.test method.

To set the timeout of the flow, set theX-Server-Timeout field in the header. By default, the timeout is 120 seconds. For a list of pre-defined set of request parameters, seeSystem parameters.

Publish an integration

Publishing an integration version deploys that integration version, and puts it in anactive state. Any previously published version of the integration will automatically be unpublished, and all the services that rely on the previously published integration version will automatically use the latest published version.

To publish an integration, select one of the following options:

Console

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

    Go to Application Integration

  2. ClickIntegrations from the left navigation menu to open theIntegrations page.
  3. Select the integration that you want to publish.

  4. In the designer navigation bar, click theVersion dropdown, and select the integration version that you want to publish.
  5. ClickPublish.

    TheAutogenerate Integration description dialog appears. If you want to generate a description, clickSure, continue. Otherwise, clickNo, just publish.

Upon successfully publishing your integration, you can view and inspect theexecution logs of the published integration. To view logs, clickLogs in the toolbar of the integration editor.

By default, Application Integration locks an integration from editing when it is published. To make any changes to the published integration, clickEnable editing in the integration editor. Editing a published integration will create a new version of that integration.

API

Call theprojects.locations.integrations.versions.publish method.

Unpublish an integration

Unpublishing anactive integration version undeploys that integration version, and puts it in asnapshot state. Any services that rely on the published version of the integration will automatically be stopped.

To unpublish an integration, select one of the following options:

Console

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

    Go to Application Integration

  2. ClickIntegrations from the left navigation menu to open theIntegrations page.
  3. Select the integration that you want to unpublish.

  4. In the designer navigation bar, click theVersion dropdown, and select the integration version that you want to unpublish.
  5. ClickUnpublish.

    After the integration is successfully unpublished, you can clickEnable editing in the integration editor to edit the integration. Editing the integration will create a new version of that integration.

API

Call theprojects.locations.integrations.versions.unpublish method.

Quota and limits

For information about Application Integration quotas and limits, seeQuotas and limits.

Best practice

Quotas and limits

For information about quotas and limits, seeQuotas and limits.

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.