See the supported connectors for Application Integration.

Test and publish integrations

You can test or publish an integration from the integration editor after you have added and configured the integration with the necessary triggers, tasks, and edge connections. When you test an integration using the Google Cloud console, the integration is executed in the synchronous mode.

Required role

To ensure that the user account has the necessary permissions to test or publish an integration, ask your administrator to grant the user account the Application Integration Service Agent (roles/integrations.serviceAgent) IAM role on the project. For more information about granting roles, see Manage access to projects, folders, and organizations.

Your administrator might also be able to give the user account the required permissions through custom roles or other predefined 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 as Approval task, Suspend task, or Timer task, cannot be tested before publishing the integration.

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

Console

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 page appears.
3. Select the integration that you want to test.

4. In the designer navigation bar, click Test.

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

5. Click Test integration.

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

   • To edit the input variables, click Edit input variables.
   • To retest the integration, click Retest integration.
   • To restore the values, click Restore values.
   • To view and inspect the execution logs of the test run, click View logs.
   • If you have enabled Cloud Logging, then to view logs in Cloud Logging, click View Cloud logs.
   • To edit the integration without creating a new version of the integration, click Edit integration.
   • To close the test operation and return to the integration editor, click Close.

API

Call the projects.locations.integrations.test method.

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

Publish an integration

Publishing an integration version deploys that integration version, and puts it in an active 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 the Application Integration page.

   Go to Application Integration

2. In the navigation menu, click Integrations. The Integrations page appears.
3. Select the integration that you want to publish.

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

   The Autogenerate Integration description dialog appears. If you want to generate a description, click Sure, continue. Otherwise, click No, just publish.

Upon successfully publishing your integration, you can view and inspect the execution logs of the published integration. To view logs, click Logs 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, click Enable editing in the integration editor. Editing a published integration will create a new version of that integration.

API

Call the projects.locations.integrations.versions.publish method.

Unpublish an integration

Unpublishing an active integration version undeploys that integration version, and puts it in a snapshot 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 the Application Integration page.

   Go to Application Integration

2. In the navigation menu, click Integrations. The Integrations page appears.
3. Select the integration that you want to unpublish.

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

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

API

Call the projects.locations.integrations.versions.unpublish method.

Quota and limits

For information about Application Integration quotas and limits, see Quotas and limits.

Best practice

• Define the usability of a variable (input variable or output variable) before testing your integration. See Integration variables.
• Define error handling for your integration.

Quotas and limits

For information about quotas and limits, see Quotas and limits.