Sie können eine Integration über den Integrationseditor testen oder veröffentlichen, nachdem Sie die Integration mit den erforderlichen Triggern, Aufgaben und Edge-Verbindungen hinzugefügt und konfiguriert haben. Wenn Sie eine Integration mit der Google Cloud -Konsole testen, wird die Integration im synchronen Modus ausgeführt.
Wenn Sie prüfen möchten, ob die Integration wie beabsichtigt funktioniert, können Sie sie vor der Veröffentlichung testen. Wenn Sie eine Integration testen, können Sie mit den Werten der Integrationseingabevariablen experimentieren und Fehler im Verbindungsablauf der Integration erkennen.
Wählen Sie eine der folgenden Optionen aus, um eine Integration zu testen:
Wenn Sie eine Integrationsversion veröffentlichen, wird sie bereitgestellt und in den aktiven Status versetzt. Alle zuvor veröffentlichten Versionen der Integration werden automatisch aus der Veröffentlichung entfernt und alle Dienste, die auf der zuvor veröffentlichten Integrationsversion beruhen, verwenden automatisch die zuletzt veröffentlichte Version.
Wählen Sie eine der folgenden Optionen aus, um eine Integration zu veröffentlichen:
Wenn Sie die Veröffentlichung einer aktiven Integrationsversion aufheben, wird die Bereitstellung der Integrationsversion aufgehoben und sie wird in den Snapshot versetzt. Alle Dienste, die auf der veröffentlichten Version der Integration beruhen, werden automatisch beendet.
Wählen Sie eine der folgenden Optionen aus, um die Veröffentlichung einer Integration aufzuheben:
Informationen zu Kontingenten und Limits für Application Integration finden Sie unter Kontingente und Limits.
Best Practice
Legen Sie die Verwendbarkeit einer Variablen (Eingabe- oder Ausgabevariable) fest, bevor Sie Ihre Integration testen. Weitere Informationen finden Sie unter „Integrationsvariablen“.
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-08-25 (UTC)."],[[["\u003cp\u003eYou can test an integration to verify its functionality and identify faults before publishing, but note that integrations with suspension-based tasks cannot be tested prior to publishing.\u003c/p\u003e\n"],["\u003cp\u003eTesting an integration in the Google Cloud console executes it in synchronous mode, allowing for the editing of input variables, retesting, and viewing execution logs.\u003c/p\u003e\n"],["\u003cp\u003ePublishing an integration version deploys it in an active state, automatically unpublishing any previous version and directing all services to the latest version.\u003c/p\u003e\n"],["\u003cp\u003eUnpublishing an active integration version undeploys it, moving it to a snapshot state and stopping any dependent services.\u003c/p\u003e\n"],["\u003cp\u003eAn user needs the Application Integration Service Agent role to get the permissions required to test or publish an integration.\u003c/p\u003e\n"]]],[],null,["# Test and publish integrations\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nTest and publish integrations\n=============================\n\n\nYou can test or publish an integration from the [integration editor](/application-integration/docs/integrations-ui-layout) after you have added and configured the integration with the necessary [triggers](/application-integration/docs/trigger-overview), [tasks](/application-integration/docs/task-overview), and [edge](/application-integration/docs/edge-overview) connections. When you test an integration using the Google Cloud console, the integration is executed in the [synchronous mode](/application-integration/docs/triggers#execution-modes).\n\nRequired role\n-------------\n\n\nTo get the permissions that\nyou need to test or publish an integration,\n\nask your administrator to grant you the\n\n\n[Application Integration Service Agent](/iam/docs/roles-permissions/integrations#integrations.serviceAgent) (`roles/integrations.serviceAgent`)\nIAM role on the project.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nYou might also be able to get\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\nTest an integration\n-------------------\n\n\nOptionally, 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.\n\n\n| **Note:** Integrations that are configured with suspension-based tasks, such as [Approval task](/application-integration/docs/approval-task), [Suspend task](/application-integration/docs/run-suspend-task), or [Timer task](/application-integration/docs/run-timer-task), cannot be tested before [publishing](#publish-integrations) the integration.\n\n\u003cbr /\u003e\n\n\nTo test run an integration, select one of the following options:\n\n### Console\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. Click **Integrations** from the left navigation menu to open the **Integrations** page.\n3. Select the integration that you want to test. \u003cbr /\u003e\n\n4. In the designer navigation bar, click **Test** .\n\n\n If you have multiple triggers configured in your integration, then select the trigger from which you want to\n test run your integration. The **Test Integration** pane appears.\n5. Click **Test integration** .\n\n\n Application Integration test runs the integration and displays the execution result in the **Test Integration** pane:\n - To edit the input variables, click **Edit input variables**.\n - To retest the integration, click **Retest integration**.\n - To restore the values, click **Restore values**.\n - To view and inspect the [execution logs](/application-integration/docs/viewing-logs) of the test run, click **View logs**.\n - If you have [enabled Cloud Logging](/application-integration/docs/cloud-logging#enable-cloud-logging), then to view logs in Cloud Logging, click **View Cloud logs**.\n - To edit the integration without creating a new version of the integration, click **Edit integration**.\n - To close the test operation and return to the integration editor, click **Close**.\n\n### API\n\n\nCall the [`projects.locations.integrations.test`](/application-integration/docs/reference/rest/v1/projects.locations.integrations/test) method.\n\nTo 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](/apis/docs/system-parameters).\n\nPublish an integration\n----------------------\n\n\nPublishing an integration version deploys that integration version, and puts it in an [active state](/application-integration/docs/integration-versions). 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.\n\n\nTo publish an integration, select one of the following options:\n\n### Console\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. Click **Integrations** from the left navigation menu to open the **Integrations** page.\n3. Select the integration that you want to publish.\u003cbr /\u003e\n\n4. In the designer navigation bar, click the **Version dropdown**, and select the integration version that you want to publish.\n5. Click **Publish** .\n\n The **Autogenerate Integration description** dialog appears. If you want to generate a description, click **Sure, continue** . Otherwise, click **No, just publish**.\n\n\nUpon successfully publishing your integration, you can view and inspect the [execution logs](/application-integration/docs/integration-execution-logs) of the published integration. To view logs, click **Logs** in the toolbar of the integration editor.\n\n\nBy 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.\n\n### API\n\n\nCall the [`projects.locations.integrations.versions.publish`](/application-integration/docs/reference/rest/v1/projects.locations.integrations.versions/publish) method.\n\n### Unpublish an integration\n\n\nUnpublishing an [active](/application-integration/docs/integration-versions) integration version undeploys that integration version, and puts it in a [snapshot](/application-integration/docs/integration-versions) state. Any services that rely on the published version of the integration will automatically be stopped.\n\n\nTo unpublish an integration, select one of the following options:\n\n### Console\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. Click **Integrations** from the left navigation menu to open the **Integrations** page.\n3. Select the integration that you want to unpublish.\u003cbr /\u003e\n\n4. In the designer navigation bar, click the **Version dropdown**, and select the integration version that you want to unpublish.\n5. Click **Unpublish** .\n\n\n 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.\n\n### API\n\n\nCall the [`projects.locations.integrations.versions.unpublish`](/application-integration/docs/reference/rest/v1/projects.locations.integrations.versions/unpublish) method.\n\nQuota and limits\n----------------\n\nFor information about Application Integration quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nBest practice\n-------------\n\n- Define the usability of a [variable (input variable or output variable)](/application-integration/docs/variables) before testing your integration. See Integration variables.\n- Define [error handling](/application-integration/docs/error-handling) for your integration.\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas)."]]
