Integration Service release notes

The Database Hub connector now sends the User-Agent identifier uipath+uipath with every API request to Databricks. This helps Databricks and administrators attribute requests in logs and during troubleshooting. No changes to authentication or activities are required.

We improved the error messaging on invalid organization ID during connection creation and update.

The HTTP Request activity is now available for the OpenAI V1 Compliant LLM connector. This activity allows you to go beyond the predefined activities in a given package and make requests to any endpoint of a vendor's API.

HTTP Request reuses the connector pre-configuration and provides transparency of headers, authentication, and query parameters. You can reuse any of your connections, and provide the endpoint and the JSON payload. Use this connector-specific HTTP Request activity to benefit from Integration Service's capabilities for connection management. To learn more, refer to the HTTP Request activity page.

Characters were not properly masked in the API key field of the connection creation page.

Characters were not properly masked in the API key field of the connection creation page.

Characters were not properly masked in the Service account key field of the connection creation page.

Optional scopes were listed under custom scopes instead of predefined scopes on the connection creation page.

We are expanding data residency support for UiPath GenAI Activities in several new regions: Canada, the European Union, India, Singapore, the United Kingdom, and the United States. Data is now stored and processed within the selected regions, helping you meet local regulatory requirements while maintaining high availability and security.

For more information, refer to Data residency in the Automation Cloud admin guide.

The following activities and triggers are no longer available in the Microsoft OneDrive & SharePoint, Microsoft Outlook 365, Gmail, Google Drive, and Google Sheets connectors for new automations:

This change affects only new automations. Existing workflows that use these generic activities or triggers will continue to run as before.

Alternatively, if a required operation is not available through the out-of-the-box activities of the connector, you can use the correspondent HTTP Request activity to call the underlying service APIs. This action enables custom or currently unsupported scenarios while maintaining full API flexibility.

We are expanding data residency support in Australia and Japan for UiPath GenAI Activities. Data is now stored and processed within the selected regions, helping you meet local regulatory requirements while maintaining high availability and security.

For more information, refer to Data residency in the Automation Cloud admin guide.

A new authentication method, OAuth 2.0 Client credentials, is now available for the Microsoft Azure OpenAI connector. This method provides a more secure way to authenticate and authorize access to the Azure OpenAI services using your client credentials.