<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Application Integration API Changes — Google Cloud Radar</title>
  <subtitle>Real-time pre-release intelligence and changelog for Google Application Integration. Tracked from Google Discovery Service.</subtitle>
  <link href="https://google-cloud-radar.com/services/application-integration/atom.xml" rel="self" type="application/atom+xml" />
  <link href="https://google-cloud-radar.com/services/application-integration" rel="alternate" type="text/html" />
  <id>https://google-cloud-radar.com/services/application-integration/atom.xml</id>
  <updated>2026-11-06T00:00:00Z</updated>
  <author>
    <name>Google Cloud Radar</name>
    <uri>https://github.com/max-ostapenko/google-cloud-radar</uri>
  </author>
  
  <entry>
    <title>New Workflow Text Proto &amp; Publish Validation</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-06-integrations-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-06-integrations-v1</id>
    <published>2026-11-06T00:00:00Z</published>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary type="text">Application Integration now supports a `WORKFLOW_TEXTPROTO` file format for specific upload/download operations, enabling a new way to manage integration definitions. Additionally, a `validateOnly` option has been added to the publish request, allowing pre-flight checks without actual deployment.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v1" />
  </entry>
  <entry>
    <title>New DATA_LAYER Error Code for CRM Logs</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-31-integrations-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-31-integrations-v1</id>
    <published>2026-10-31T00:00:00Z</published>
    <updated>2026-10-31T00:00:00Z</updated>
    <summary type="text">The `CrmlogErrorCode` schema in Application Integration now includes a new `DATA_LAYER` enum value for `commonErrorCode`. This expands the set of identifiable error types for CRM log entries.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v1" />
  </entry>
  <entry>
    <title>Test Unpublished Integration Drafts</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-integrations-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-integrations-v2</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">The `PostToQueueWithTriggerIdRequest` schema now includes a `workflowId` field, allowing you to target specific, even unpublished, versions of your integrations for testing.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Change &amp; Enhanced Testing for Integrations</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-integrations-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-integrations-v1</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">A breaking change has made the `eucHardeningDisposition` field read-only in `IntegrationVersion`. Additionally, new parameters and response fields are available for `TestIntegrationsRequest` and `TestIntegrationsResponse`, offering more control and insight into credential flows and EUC hardening during integration testing.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v1" />
  </entry>
</feed>