Integration Service release notes

The Client Certificate Authentication method is available for the Microsoft OneDrive and SharePoint and Microsoft Outlook 365 connectors.

We now offer unified documentation for Integration Service across Automation Cloud and Test Cloud, Automation Cloud Public Sector and Test Cloud Public Sector.

You can now find all user and API information in a single, consistent set of guides. The release notes are also now available in one guide, organized into separate chapters for each cloud offering.

This update is part of a broader effort to create a unified documentation experience for UiPath cloud offerings, which will expand to include more products over time. For details, refer to Unified documentation experience for UiPath cloud offerings.

Integration Service is now available through Unified Pricing, our innovative licensing paradigm that brings new licensing plans, user licenses, and a consolidated consumption unit. For details on the Integration Service consumption logic, refer to the Integration Service user guide.

For extensive release notes, refer to the Automation Cloud release notes. For overview licensing information, refer to the Automation Cloud admin guide and the Overview guide.

We are introducing a major enhancement to how Integration Service usage is measured and billed, across both Flex and Unified Pricing licensing models. This new consumption model increases transparency, scalability, and predictability for API-based automations, while eliminating redundant billing for RPA workflows.

Integration Activities: the new metering unit

Integration Service uses executed Integration Activities as the standard consumption unit. This represents each time an integration activity (such as an API call through a connector) runs as part of an automation.

Depending on your licensing model, executed activities are charged as follows:

Additionally, only specific automation types now meter and charge Integration Service activities:

Robots and serverless executions remain fully licensed under their runtime costs, with no additional charges for Integration Service usage. While traditional RPA workflows with Integration Service activities now run free of additional cost, API workflows are purpose-built for scalable, high-performance API automation. They offer: precise control over API behavior, faster execution without UI dependencies, clear, tenant-level consumption reporting, and a more modern, elastic architecture for enterprise-grade API operations.

Better control and forecasting

With this new metering model, Integration Activities provide more predictable and consistent metering. Under Flex, you continue to receive API call bundles, and Integration Activities simply draw from that pool.

The HTTP and Orchestrator connectors are now generally available.

The Microsoft Azure Active Directory connector now supports client certificate-based authentication.

A new HTTP Request activity is now available, allowing 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.

This activity is available only in API workflows and agentic processes created in UiPath Maestro^TM .

To learn more, refer to the HTTP Request activity page.

The Snowflake connector now supports Personal Access Token authentication.

The callback URL is now displayed on the connection page when you create an OAuth 2.0 Authorization code connection.

The Database Hub connector is now available in preview.

Starting November 19, 2025, Integration Service API calls will transition from the current promotional period to consumption-based billing. We will resume monitoring and reporting API call usage, with a new pricing unit in effect. This update reflects improvements to our API automation licensing.

Detailed documentation and the full announcement will be available in the release notes at release time. Keep an eye out for the official update.