FIFO message processing with Pub/Sub ordering keys
Application Integration now supports publishing messages to Google Cloud Pub/Sub topics using ordering keys, enabling First-In, First-Out (FIFO) message processing. By setting an ordering key in the Pub/Sub trigger's Publish Message action, you can ensure messages are received in the correct order, enhancing reliability for integrations requiring ordered message processing. For more information on how to use ordering keys to publish messages, see Using ordering keys.
Troubleshoot failed execution logs using AI
You can now use AI-powered troubleshooting with Google Gemini to analyze failed execution logs, identify root causes, and receive precise, actionable steps to resolve errors. To use this feature, you must enable AI capabilities in your Google Cloud region. For more information, see Troubleshoot failed execution logs using AI.
]]>Manage Application Integration resources using custom constraints
You can now use custom constraints with Organization Policy to provide more granular control over specific fields for some Application Integration resources. For more information, see Manage Application Integration resources using custom constraints. This feature is now available in Preview.
]]>Salesforce connected app requires installation for OAuth 2.0 authentication
A new security requirement from Salesforce restricts the use of uninstalled connected apps. To ensure your Salesforce triggers remain functional, you must install the connected app in your Salesforce account.
When establishing a new Salesforce trigger using OAuth 2.0 authentication, you are now required to install the connected app within your Salesforce account. This step is also necessary for existing triggers using OAuth 2.0 authentication if the connected app is not already installed, as failure to do so may cause them to stop working.
For more information, see Install the OAuth 2.0 connected app.
]]>Standard canvas view
The integration editor now features a single, standard canvas view. The legacy canvas is no longer available.
]]>Cloud Function Task adds support for Cloud Functions v2 API
The Cloud Function task in Application Integration now lets you create, link, and run the latest generation of serverless functions, called Cloud Run functions, using the Cloud Functions v2 API.
For more information, see Cloud Function Task.
Control HTTP call access by region in Application Integration
Application Integration now offers a new control within the Regions page to enable or disable HTTP calls for integrations on a per-region basis.
For more information, see Manage regions.
]]>New Canvas View is enabled by default in the Integration Editor
The new Canvas View is now enabled by default in the integration editor. This change is a default setting and no manual enablement is required. You can switch to the old canvas view by disabling the New canvas view toggle.
For more information, see Use the new canvas view.
]]>Build Conversational Agents with Dialogflow CX (Preview)
Application Integration now simplifies the creation of conversational experiences with direct integration with Conversational Agents (Dialogflow CX). Using API triggers, you can now build intelligent chatbots and automated tools directly within your integration workflows, enhancing user interactions and automating tasks.
For more information, see Build conversational agents with Application Integration.
Enhancements to Replay Execution
Application Integration Replay Execution now provides the following enhancements:
For more information, see Introduction to replay executions.
]]>Enhancements to Execution Logs
Application Integration Execution Logs now provides the following enhancements:
For more information, see View execution logs.
]]>Deprecation of Rhino engine for JavaScript Task
Effective January 24, 2025, Application Integration will no longer support Rhino as the JavaScript execution engine. All existing published JavaScript tasks will continue to use Rhino and can be migrated to V8 manually. Newly created JavaScript tasks will exclusively use V8.
For more information, see JavaScript execution engine. This deprecation is related with CVE-2025-0982.
You will not be able to use the Send email task in your integrations if you have enabled VPC service perimeter for the Application Integration service.
]]>Config variables pane (Preview)
You can now view and edit all the config variables defined within your integration using the new Config Variables pane. For more information, See View and edit config variables.
]]>Dynamic Backend Authentication support for Connectors
Application Integration now supports dynamic backend authentication for connectors. Enable Authentication Override in Integration Connectors to allow your connections to seamlessly switch between authentication methods during runtime.
For more information, see Configure authentication override.
]]>You can now build and publish custom connectors for Google Cloud Marketplace. This feature is in preview.
The following connectors built by partners are available in the Google Cloud Marketplace. You can use these connectors to create connections and use them in Application Integration.
Integration templates (Preview)
Save time and effort building integrations with integration templates. These pre-defined blueprints provide a starting point for common integration flows, allowing you to quickly create and customize integrations without starting from scratch.
For more information, see Templates.
Generate and view OpenAPI Specification (Preview)
You can now generate and view the OpenAPI Specification for any published integration that uses API triggers. This allows for greater understanding and analysis of your integration's API interactions.
For more information, see View OpenAPI Specification for your integration.
API trigger input and output variables
You can now set request and response payloads for an API trigger using trigger specific input and output variables. For more information, see API trigger.
]]>JavaScript task using Gemini
If your integration flow requires any complex data mapping logic, Gemini can now recommend a JavaScript task. For more information, see Create an integration using Gemini.
You can add a JavaScript task, edit an existing task, or use Gemini to help understand the JavaScript code. For more information, see Configure JavaScript tasks.
]]>Add failure policy (Generally available (GA))
You can now configure more complicated retry strategies for tasks, such as retries based on the error codes or the variable values during the execution:
ExecutionMode and ErrorInfo.For more information, see Example for error handling.
]]>Build integrations with Gemini Code Assist (GA)
Building integrations with Gemini Code Assist is now generally available (GA).
Additionally, if you have API Hub enabled in your project, then Gemini can assist you to provide contextually appropriate Call REST Endpoint tasks and task configuration recommendations based on the logical flow of your existing integration. For more information see, Configure Call REST API tasks.
]]>Diagram mode in the Data Transformer Task (Preview)
The Diagram mode provides a console-based experience to select the input and output variables and perform transformations in the data transformation editor. For more information, see the Data Transformer task.
Replay execution (Preview)
You can now rerun a failed integration with the same parameters as the previous execution. For more information, see Replay executions.
Cancel execution (Preview)
If you have executions that are suspended due to an approval task or a technical issue, you can now choose to cancel those executions. For more information, see Cancel executions.
Test cases (Preview)
You can now test if your integration is working as intended by creating and running test cases on your complex integrations.
For information about test case, see Introduction to test cases. Learn how to do the following:
Local logging in async mode (Generally available (GA))
By default, local logging for new integrations is now enabled in async mode. With this change, the log data is persisted (written) at fixed intervals or after the completion of the integration's execution, whichever is earlier. You can change the default settings by editing the integration details.
For more information, see Local logging.
]]>View logs in Cloud Logging
Viewing integration execution logs in Cloud Logging is now generally available (GA). For more information, see View logs in Cloud Logging
]]>The Resolve JSON Path data transformer function is now available. This function resolves a JSON path on a given JSON object by using the JSONPath reference.
The XSLT Transform data transformer function is now available. This function transforms the specified XML string using the specified XSL string.
]]>New canvas view
In the integration editor layout, you can try the new canvas view to create integration flows. This feature is in preview. The canvas view offers the following benefits:
In the Application Integration editor, you can now search, browse, and select tasks and connectors in the Tasks list. For more information, see Add a Connectors task.
]]>The Solace trigger is now available in preview.
]]>You can now share custom connectors between different Google Cloud projects by exporting and importing the connector specification. This feature is in preview.
]]>The following Connector Event triggers are generally available:
]]>The TIBCO EMS trigger is now available in preview.
]]>Application Integration is now available in Milan (europe-west8). For a list of supported regions, see Application Integration locations.
Terraform support
You can now use Terraform to provision new regions and create authentication profiles. For a detailed reference document about terraform resources, see google_integrations_client and google_integrations_auth_config.
Loop Metadata variables are changing
In the For each loop and While loop tasks, there's a Loop metadata variable in which you will find duplicate keys for the output variable–for example, Current Iteration Count and current_iteration_count. We recommend you to use the variables that contain the underscore (_) symbol because the other keys are being deprecated.
For more information, see Known issue: Duplicate keys in the Loop metadata.
]]>