MCP connector is now available in preview
Integration Connectors support the Model Context Protocol (MCP) connector. You can use this connector to create and configure connections for secure data exchange and operations in your business applications. Within Application Integration, you can use MCP through a Connectors task.
]]>Apigee API hub connector is now available in preview
Integration Connectors now support the Apigee API hub connector. You can use this connector to discover, manage, and govern your APIs in Apigee API hub.
]]>HL7 Connectors now support new actions
The HL7 connector now supports the following new transformation actions:
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 connections remain functional, all users must install connected app in your Salesforce account.
When establishing a new Salesforce connection using OAuth 2.0 authentication, you are now required to install the connected app in your Salesforce account. This step is also necessary for existing connections 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 connected app.
]]>The customer-managed encryption keys (CMEKs) feature is now generally available (GA).
]]>You can use the following connectors that are now available in Google Cloud Marketplace to create connections and use them in Application Integration.
The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>The ZATCA connector is now available in Google Cloud Marketplace. You can use this connector to create connections and use them in Application Integration.
The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>You can now use a Google-managed OAuth client instead of creating your own client for the following connectors, which are in preview:
]]>The Microsoft Exchange connector is now GA.
To view the list of all the GA connectors, see Connectors in GA.
]]>The following connectors are now generally available (GA):
]]>The Azure AD connector now supports event subscription which you can leverage in your integrations by using the Azure AD trigger. This trigger is available in preview.
]]>Integration Connectors now supports customer-managed encryption keys (CMEKs). This feature is in preview.
The HL7 connector is now available in preview. The connector also supports event subscription, which you can leverage in your integrations by using the HL7 trigger.
]]>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 Google Cloud Marketplace. You can use these connectors to create connections and use them in Application Integration.
The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>The BigQuery connector now supports the Array data type.
]]>The private network connectivity documentation has been restructured to include information about the following networking patterns:
]]>The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>The Microsoft Teams connector is now generally available (GA).
To view the list of all the GA connectors, see Connectors in GA.
]]>The OneDrive connector is now generally available (GA).
To view the list of all the GA connectors, see Connectors in GA.
The BigQuery connector now supports OAuth 2.0 - Authorization code.
Connection names cannot exceed 49 characters. Previously, connection names had a limit of 63 characters.
]]>Connectors for Google services
When you use OAuth 2.0 - Authorization code authentication in Google services connectors, you can select the applicable scopes from the drop-down. Previously, you had to enter comma separated values for OAuth 2.0 scopes.
HTTP connector
Use the Status Check field to check the status of an HTTP connection by specifying an endpoint URL, which can include an endpoint attachment IP address.
]]>The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>The Neo4j connector is now generally available (GA).
]]>The following connectors are now generally available (GA):
]]>The TIBCO EMS connector is now generally available (GA). The connector also supports event subscription, which you can leverage in your integrations by using the TIBCO EMS trigger.
The following connectors are now generally available (GA):
To view the list of all the GA connectors, see Connectors in GA.
]]>You can configure a connector to collect logs for the following severity levels:
For more information, see View Integration Connectors logs.
]]>The Solace connector is now available in preview. The connector also supports event subscription, which you can leverage in your integrations by using the Solace trigger.
]]>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 connectors support event subscription:
You can use the eventing feature in Application Integration through the SAP ERP trigger and SAP Gateway trigger respectively.
]]>